What is Pure Component? When should you use Pure Component instead Component?
Thread Tags
Adobe Illustrator Adobe InDesign Adobe Photoshop Android Development Android Programming Android Studio Automation Testing C / C++ Programming Career Options College Lounge css digital marketing Digital Marketing / SEO Fireworks Graphic Design Graphic designing Graphics Design Graphics Designing HTML? Illustrator Internship Training logo Design logo designing Magento Photoshop PHP Programming QA react-native Scroll Website SEO Single Page Website Stock Managment System Testing Typography UI UI/UX Development UI Design UI Designing UI development User Interface UX Design Web Designing Website Design Wordpress wpRegister 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.
Register Now, or check out the Site Tour and find out everything Smart Mentors has to offer.
This thread contains 1 reply, has 2 voices, and was last updated by darshan.soni007 2 years, 2 months ago.
- Author Replies
- January 30, 2019 at 12:30 pm #52887
– Pure Component is specifically the same as Component except that it handles Component Update method for us. When props or state changes, Pure Component will do a shallow comparison on both props and state. Component won’t compare current props and state to next out of the box. Thus, the component will re-render by default – whenever should Component Update is called.
– When analyzing previous props and state to next, a shallow comparison will check that primitives have the same value and that the references are the same between more complex javascript values like objects and arrays.
– It is enough to prefer Pure Component over Component whenever we never change our objects.
- AuthorPosts
You must be logged in to reply to this thread.Please login or register. Registration is 100% free.