Hi i am trying, but facing huge difficulties in converting a jQuery MVC app into React Web Api app, can somebody please help me, I though I can easily take all that's there in the convert easily into React but, i have come across lots of difficulties, one such is, importing css styles, and referring multiple css classes (in jQuery they can put multiple css classes in one element, but I am not able to do it in jsx files).
Now I am just thinking, can i just put all those js files into a folder just reference them into my jsx files or components, can somebody please help me in this regards? How can I do it and what difficulties am I going to face, how can I call those methods within js files of jQuery into my jsx components, any help please - I would be very very thankful friends.
I am also trying in my way by googling, reading online, asking friends and colleagues - but if anybody has faced these issues before could be helpful for me - thank you
I don't have much experience with React, for I chose Angular instead. Angular and React are similar in design and sort of the same. Last year, I tried to convert my website which I wrote in .Net Core MVC, Razor, JQuery and Mobirize over to Angular.
I did what you are doing ...
Next I worked on the cool Mobirise CSS styles, effects and animations. I wanted my project to be free of CSS, and chose SCSS instead, so I translated all of the Mobirise CSS into SCSS one style at a time and tested them and got good results.
So I was finally ready to do a dump of all the old technology and go with the new technology to produce a clean project. I dumped JQuery completely, Went SCSS, and worked on my Webpack, node-sass and build or package.json file. My project was a mess and all the old technology that was removed left me with a basket full of holes or missing things. I fixed or replaced one thing at a time and got 95% of it working.
So what did I learn?
I learned that the old way of how a website works does not apply to technologies such as Angular, React and Vue. It's a totally different way of thinking, which includes how your Models are designed, getting more CRUD like in how you design forms and your API calls, and even down to database document designs. With efficient models, db documents, and even SCSS classes, you can really simplify a project down to the bare bones with very few lines of code and HTML.
I don't think you have enough experience with not just React, but how this new technology works in general. You need to realize that you need to start from the ground up and explore the new possibilities that exist out there with React and dump the old way of doing things. If this CARB project your working on was sold as a React upgrade using the existing database servers and models, your going to be fighting this for years. That's why I was concerned as a California resident and my gas tax money being spent on this.
Check out my website link below, it's the project I'm talking about; my conversion from .Net Core MVC to Angular. And also a database conversion from SQL to Document based. You can GTMetrix the project as well to see the small footprint I created as well with super compression using webpack.
If it ain't broke don't fix it
Discover my world at jkirkerx.com
I too understood that, i need to build the whole front end design from scratch with React. Another thing is, its not that whole project converting from jQuery to React, its a prototype I am trying to make. This project that I am working isn't a live project, its just a small prototype project I am doing now.
Since the React and jQuery operates differently, conversion of jQuery or even using jQuery isn't an option in React, better to build it from the scratch.
This is an with couple of pages for prototype to show how single page App works.
I am not into Contracting anymore buddy - I am an employee, but this is prototype app. It is not an enterprise app yet, this app isn't launched yet, it seems we need to write it from the scratch.
The reason why I was going in that direction was, it has jQuery libraries which have click etc events written and reading all those and implementing them again I thought may take longer time, but actually if it takes let it, that's what it is.
You know right reading jQuery is like more challenge, that's why mostly these readable front end scripts like React Angular came in. I too did around 6 months of work on Angular, but React is little different than Angular in terms of syntax etc but yes I feel routing was much similar except we need to import rounting explicitly.
Before Document Printing: add the file name to the Header (permanently, by the way). PDF-Exchange has what they call Watermarks which I currently use on a manual basis - Dynamic Stamps, too but just to add a date stamp.
So I created this user interface to manage the sub categories of a category.
I have the whole document loaded in Angular V7+ as a model, and I just list the sub categories in a table.
Now I have a search interface in which I'd like to query to sub categories to find a specific one.
In all my other uses of search, I call a service to .Net Core and let core find the answer and return them. Well that's easy because I'm loading documents. But this time I'd like to just search the model in the DOM. In other words find the data within the document. This way I can edit the document and return the whole document upon a change and let Core update it.
So I can find the Sub Category, but I'd like to reorder the array. Show the search results first and then the rest in TypeScript. Right now I'm just loading the result in a Modal UI for editing. But I will run into this in the future so I should figure it out.
Not sure if I'm approaching this right or not as far as my document design goes. Of if it's not feasible to do and I should write a service for it and let Core do the work.
I'm getting closer now.
Getting better with push, unshift and splice now.
I changed the way the interface works, where I can now reload the original sub categories after search with a reload button. And instead of sending the category back to the .Net API, I rewrote the API to work with one sub category at a time.
Just need to figure out how to get more than 1 result back.