Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: update dynamic import terminology #42

Merged
merged 3 commits into from Feb 3, 2021

Conversation

shesmer
Copy link
Contributor

@shesmer shesmer commented Feb 1, 2021

No description provided.

text/0110-dynamic-components.md Outdated Show resolved Hide resolved
@@ -331,7 +337,7 @@ The compiler add to its metadata all of the parsed dynamic imports, its source v

## Drawbacks

The biggest drawback of this feature is the historic abuse of dynamic component creation in the Lightning Platform. We will add guardrails to prevent developers from shooting themselves in the foot.
The biggest drawback of this feature is the historic abuse of dynamic imports in the Lightning Platform. We will add guardrails to prevent developers from shooting themselves in the foot.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is also the case of dynamic component instantiation. Some developers are using this approach while branching in the template (using if:true, if:false) is preferable.

Co-authored-by: Pierre-Marie Dartus <dartus.pierremarie@gmail.com>
@pmdartus pmdartus merged commit 566aad1 into salesforce:master Feb 3, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants