Which Lifecycle Event Do You Make Ajax Requests And Why?
Thread TagsAdobe Illustrator Adobe InDesign Adobe Photoshop Android Development Android Programming Android Studio Automation Testing C / C++ Programming Career Options College Lounge css designed Design layout digital marketing Digital Marketing / SEO Fireworks Graphic Design Graphic designing Graphics Design Graphics Designing HTML? Illustrator Internship Training logo Design logo designing mobile phones Photoshop QA react-native Scroll Website SEO Single Page Website Testing Typography UI UI/UX Development UI Design UI Designing UI development User Interface UX Design Viewport Web Designing web pages Website Design
Log in with your username and password
Register for free!
Registration at Smart Mentors is completely free and takes only a few seconds. By registering you’ll gain:
- Full Posting Privileges.
- Access to Private Messaging.
- Optional Email Notification.
- Ability to Fully Participate.
- Author Replies
- January 22, 2019 at 12:09 pm #52275
AJAX requests should go in the componentDidMount lifecycle event.
There are a few reasons for this,
– Fiber, the next implementation of React’s reconciliation algorithm, will have the capacity to start and stop rendering as required for performance gains. One of the trade-offs of this is that componentWillMount, the other lifecycle event where it might make sense to make an AJAX request, will be “non-deterministic”. What this means is that React may start requesting componentWillMount at various times whenever it feels like it needs to. This would obviously be a bad formula for AJAX requests.
– You can’t support the AJAX request won’t fix before the component mounts. If it did, that would mean that you’d be trying to setState on an unmounted component, which not only won’t work. Doing AJAX in componentDidMount will ensure that there’s a component to update.
You must be register. Registration is 100% free.to reply to this thread.Please or