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

Change Error Span for "Function X has some invalid arguments" #2284

Merged
merged 6 commits into from
Mar 29, 2024

Conversation

lesaltzm
Copy link
Contributor

Moves the error span for "some invalid arguments" to just the head of the call node, so it doesn't hide/distract from other more specific errors in the formula bar

@lesaltzm lesaltzm requested a review from a team as a code owner March 28, 2024 20:21
@LucGenetier
Copy link
Contributor

✅ No public API change.

Copy link
Contributor

@CarlosFigueiraMSFT CarlosFigueiraMSFT left a comment

Choose a reason for hiding this comment

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

:shipit:

@lesaltzm
Copy link
Contributor Author

Do not merge, pending test in PA Client

@LucGenetier
Copy link
Contributor

✅ No public API change.

@lesaltzm lesaltzm merged commit 241fe1d into main Mar 29, 2024
4 checks passed
lesaltzm added a commit that referenced this pull request Apr 22, 2024
This fixes a nullref that's always been possible in
ErrorContainer.HaserrorsInTree Following #2284 it was more common that
errors had only a token and not a node. This wasn't handled in this
function.
lesaltzm added a commit that referenced this pull request Apr 22, 2024
This fixes a nullref that's always been possible in
ErrorContainer.HaserrorsInTree Following #2284 it was more common that
errors had only a token and not a node. This wasn't handled in this
function.
lesaltzm added a commit that referenced this pull request Apr 22, 2024
This fixes a nullref that's always been possible in
ErrorContainer.HaserrorsInTree Following #2284 it was more common that
errors had only a token and not a node. This wasn't handled in this
function.
lesaltzm added a commit that referenced this pull request Apr 22, 2024
This fixes a nullref that's always been possible in
ErrorContainer.HaserrorsInTree Following #2284 it was more common that
errors had only a token and not a node. This wasn't handled in this
function.
lesaltzm added a commit that referenced this pull request Apr 25, 2024
This fixes a nullref that's always been possible in
ErrorContainer.HaserrorsInTree Following #2284 it was more common that
errors had only a token and not a node. This wasn't handled in this
function.
lesaltzm added a commit that referenced this pull request Apr 25, 2024
This fixes a nullref that's always been possible in
ErrorContainer.HaserrorsInTree Following #2284 it was more common that
errors had only a token and not a node. This wasn't handled in this
function.
lesaltzm added a commit that referenced this pull request Apr 25, 2024
This fixes a nullref that's always been possible in
ErrorContainer.HaserrorsInTree Following #2284 it was more common that
errors had only a token and not a node. This wasn't handled in this
function.
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.

3 participants