[DOC] Removed arguments from willDestroy for Glimmer components#21100
Merged
NullVoxPopuli merged 1 commit intoemberjs:mainfrom Mar 3, 2026
Merged
[DOC] Removed arguments from willDestroy for Glimmer components#21100NullVoxPopuli merged 1 commit intoemberjs:mainfrom
NullVoxPopuli merged 1 commit intoemberjs:mainfrom
Conversation
Contributor
Estimated Asset SizesDiff Details
|
922a7e6 to
dfcdd04
Compare
NullVoxPopuli
approved these changes
Mar 3, 2026
dfcdd04 to
f66efa9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Background
In a production project, I saw that developers had written the following,
when this would suffice:
The source code for
GlimmerComponentshows thatwillDestroydoesn't take any arguments, but the API Guides still claim that it does (I'm guessing based on what had happened with the classic Ember component?).