While it's not ReactJS, my team is rebuilding our 10+ year old website with AngularJS, Elastic Search and CF2016's Rest Services.
Setting up a Rest service in CF is pretty straightforward, although it can be very tricky to debug if there is an issue. For instance, the error reporting when refreshing your Rest service rarely will provide useful information. If you're lucky, it will tell you the file that is causing the issue, but not where in the file. Other times it tells you EVERY file has an issue. The only way to get around that is to check the Exception logs. Case sensitivity was always an issue with CF and JSON. We struggled with that for awhile until update 2 was applied across the environments. That saved us a lot of time. Type casting in JSON was also an issue that is now fixed in one of the updates. There were several times where forehead met the keyboard when trying to convert a query result to JSON, but CF decided one field was a number instead of a string when serializing the results. But the biggest issue of all is not related to any of the technology or languages. It's been a huge P.I.T.A. to figure out and/or remember the business logic that has been in place for over a decade on a site that was not well written :) Kevin On Mon, Feb 26, 2018 at 9:16 PM, Ajas Mohammed <ajash...@gmail.com> wrote: > Just wondering if anyone working with CF plus ReactJS. Please let us know > or share your experience. > > It will be fun to discuss a use case for this combination. > > Thanks, > -- > <Ajas Mohammed /> > iUseDropbox(http://db.tt/63Lvone9) > http://ajashadi.blogspot.com > We cannot become what we need to be, remaining what we are. > No matter what, find a way. Because thats what winners do. > You can't improve what you don't measure. > Quality is never an accident; it is always the result of high intention, > sincere effort, intelligent direction and skillful execution; it represents > the wise choice of many alternatives. >
