feat(errors): update error messaging to provide solutions #3001
Conversation
This file contains 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
Pull Request Test Coverage Report for Build 2858
💛 - Coveralls |
|
|
||
| if (isNil(index)) { | ||
| message += `. Please make sure that the "${key.toString()}" property is available in the current context.`; | ||
| message += `.\nPlease make sure that the "${key.toString()}" property is available in the current context.`; | ||
| return message; |
There was a problem hiding this comment.
We should add potential solutions here as well.
(side note: index is nil when the property-based injection is used - no constructor. The rest remains the same)
…or-message-updates
…or-message-updates
3 tasks
|
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
What is the new behavior?
Updated error messaging to provide solutions and pinpoint where the issue is stemming from.
Does this PR introduce a breaking change?
Other information