Switch settings sections and form elements to created lifecycle hook #5224
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Switch settings sections and form elements to created lifecycle hook
Pull Request Type
Related issue
Part of Development Chore: Performance: Switch from
mounted
tocreated
hook, where possible to avoid unnecessary component updatesDescription
The
mounted
lifecycle hook is triggered after the component has been rendered and has been added to the DOM, thecreated
lifecycle hook is after the component instance has been created, so props and computed properties can be accessed as well as the watchers being active. So to set the default value of a form element for example, we want to use thecreated
lifecycle hook, as setting that in themounted
hook will trigger a re-render and changes to the DOM.There are of course exceptions, if you want to show a loading symbol, then fetching the data and setting values in the mounted hook is a great idea, because then the user will see the loading icon while your stuff is running.
Testing
Desktop