1
8
Fork
You've already forked miette
0

how can i read source_back when call with_source_code before #406

Open
opened 2024年09月26日 10:16:51 +02:00 by hardfist · 1 comment
hardfist commented 2024年09月26日 10:16:51 +02:00 (Migrated from github.com)
Copy link

it's sometimes useful to get source_code as string back if we need to convert miette report to other diagnostic info like vscode lsp format, but it seems impossible to get it back, so it seems we need to wrap our own diagnostic to save source_code, but I'm not sure it's a good practice

struct MyDiagnostic{inner: Arc<miette::Report>,source_code: Arc<src>}
it's sometimes useful to get source_code as string back if we need to convert miette report to other diagnostic info like vscode lsp format, but it seems impossible to get it back, so it seems we need to wrap our own diagnostic to save source_code, but I'm not sure it's a good practice ```rs struct MyDiagnostic { inner: Arc<miette::Report>, source_code: Arc<src> } ```
Owner
Copy link

You should be able to downcast any Report into a dyn Diagnostic, and then call .source_code() on it, to get the source code, if available.

You should be able to downcast any `Report` into a `dyn Diagnostic`, and then call `.source_code()` on it, to get the source code, if available.
Sign in to join this conversation.
No Branch/Tag specified
main
zkat/typed-report
v7.6.0
miette-derive-v7.6.0
v7.4.0
miette-derive-v7.4.0
v7.3.0
miette-derive-v7.3.0
v7.2.0
miette-derive-v7.2.0
miette-derive-v7.1.0
v7.1.0
miette-derive-v7.0.0
v7.0.0
miette-derive-v6.0.1
v6.0.1
miette-derive-v6.0.0
v6.0.0
miette-derive-v5.10.0
v5.10.0
miette-derive-v5.9.0
v5.9.0
miette-derive-v5.8.0
v5.8.0
miette-derive-v5.7.0
v5.7.0
miette-derive-v5.6.0
v5.6.0
miette-derive-v5.5.0
v5.5.0
miette-derive-v5.4.1
v5.4.1
miette-derive-v5.4.0
v5.4.0
miette-derive-v5.3.1
v5.3.1
miette-derive-v5.3.0
v5.3.0
v5.2.0
miette-derive-v5.2.0
miette-derive-v5.1.1
v5.1.1
miette-derive-v5.1.0
v5.1.0
miette-derive-v5.0.0
v5.0.0
miette-derive-v4.7.1
v4.7.1
miette-derive-v4.7.0
v4.7.0
miette-derive-v4.6.0
v4.6.0
miette-derive-v4.5.0
v4.5.0
miette-derive-v4.4.0
v4.4.0
miette-derive-v4.3.0
v4.3.0
v4.2.1
v4.2.0
v4.1.0
v4.0.1
miette-derive-v4.0.0
v4.0.0
miette-derive-v3.3.0
v3.3.0
miette-derive-v3.2.0
v3.2.0
v3.1.0
v3.0.1
v3.0.0
v3.0.0-beta.0
v3.0.0-alpha.0
miette-derive-v2.2.0
v2.2.0
miette-derive-v2.1.2
v2.1.2
v2.1.1
v2.1.0
v2.0.0
miette-derive-v2.0.0
v1.1.0
1.0.1
1.0.0
1.0.0-beta.1
0.13.0
0.12.0
0.11.0
0.10.0
0.9.0
0.8.1
0.8.0
0.7.0
0.6.0
0.5.0
0.4.0
0.3.1
0.3.0
0.2.1
0.2.0
0.1.0
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
zkat/miette#406
Reference in a new issue
zkat/miette
No description provided.
Delete branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?