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.

Sign up for GitHub

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

Jump to bottom

Push error span extraction down to the point where errors are created #1165

Closed
alecthomas opened this issue Apr 4, 2024 · 2 comments
Closed

Push error span extraction down to the point where errors are created #1165

alecthomas opened this issue Apr 4, 2024 · 2 comments
Assignees
@wesbillman

Comments

@alecthomas
Copy link
Collaborator

alecthomas commented Apr 4, 2024 •
edited
Loading

While this is probably okay as a stop-gap, we should really be extending the error type to include range information so we can include it when the errors are created, as this is incredibly inefficient.

Originally posted by @alecthomas in #1163 (comment)
@github-actions github-actions bot added the triage Issue needs triaging label Apr 4, 2024
@alecthomas alecthomas changed the title Push error span extraction down to the point where they're created Push error span extraction down to the point where errors are created Apr 4, 2024
@github-actions github-actions bot removed the triage Issue needs triaging label Apr 4, 2024
@alecthomas alecthomas mentioned this issue Apr 4, 2024
Open
@wesbillman
Copy link
Member

also tracked here: #1158

@alecthomas
Copy link
Collaborator Author

Nice! Close this DUPE!

@alecthomas alecthomas closed this as not planned Won't fix, can't repro, duplicate, stale Apr 4, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@wesbillman wesbillman

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@alecthomas @wesbillman