plugin reported diagnostic for invalid span when #9246
Unanswered
bipedal-eel
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I build a memberOrder.grit thing.
My knowledge of gritql and other tools like it is very limited and the Gpt is rarely ever helpful, so please forgive the thing im about to write.
This is an excerpt of the plugin:
Basically the idea is to compare every class member and the member_after.
I am aware of
bubbleand yes this works:$class <: contains bubble $member where { ...and the "recursive" call in recursion_aaaaa can be removed, however biome check takes 3-5 times longer.That already puts a question in my head that I cannot articulate.
Furthermore the "recursive" call can be called without parameters for some reason, which adds another question: What?
The main reason im here though is that when this finds at least one error e.g. (decorated props should be before props):
This gets logged
ℹ Plugin memberOrder reported one or more diagnostics, but it didn't specify a valid span. Diagnostics have been shown without context.
/lib/src/test.ts:7:3 plugin
✖ Properties must be after static and decorated Properties: @decor() private readonly _testsss = "";
Its one info per file followed by every error in said file.
Anyone got an Idea for why theℹ is getting logged?
Knowledge as to why this works at all woud also be appreciated
Beta Was this translation helpful? Give feedback.
All reactions