fix(inject): include key name in inject() warning when called outside setup#13368
Open
ifer47 wants to merge 1 commit into
Open
fix(inject): include key name in inject() warning when called outside setup#13368ifer47 wants to merge 1 commit into
ifer47 wants to merge 1 commit into
Conversation
… setup When inject() is called outside of setup() or functional components, the warning message now includes the injection key, making it easier to identify which injection is causing the issue. Closes vuejs#13287 Co-Authored-By: zhipu/glm-5 <zai-org@claude-code-best.win>
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
1 participant
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.
Summary
inject()warning message when it is called outside ofsetup()or functional componentsinject() can only be used inside setup() or functional components.with no indication of which key was being injected(key: "keyName")in the warning, making it easy to identify which injection call is problematicProblem
When using libraries like Nuxt UI that call
inject()at the wrong time, developers see the warning but have no way to know which specific injection is causing the issue. This makes debugging difficult, especially in large applications with many inject calls.Changes
Modified
src/v3/apiInject.tsline 73 to include the key in the warning:inject() can only be used inside setup() or functional components.inject() can only be used inside setup() or functional components. (key: "foo")Closes #13287
🤖 Generated with Claude Code Best