Skip to content

Conversation

@JonatanWaern
Copy link
Contributor

Allows to differentiate errors from other extensions
(and between analysis and linting)

Signed-off-by: Jonatan Waern jonatan.waern@intel.com

@JonatanWaern
Copy link
Contributor Author

I am a bit conflicted on what is suitable to report as source. ATM I report as "dls-analysis" or "dls-lint" which is useful for people who known what the 'dls' is. But it is of little use to people who may want to identify which extension causes the error report (in which case we should probably use or even . However not only does that get quite long as a source identifier, the DLS is supposed to be client-agnostic, so adding the extension name in the source makes little sense.

@TSonono
Copy link

TSonono commented Jun 24, 2025

Another option is dmlc for analysis and dml-lint for lint. Even though these terms might not be 100 % correct, I think they could perhaps be easier to understand for a user? It's also client agnostic

@JonatanWaern
Copy link
Contributor Author

Another option is dmlc for analysis and dml-lint for lint. Even though these terms might not be 100 % correct, I think they could perhaps be easier to understand for a user? It's also client agnostic

I do not think "dmlc" is an improvement over "dls". but "dml" might be? so we could use "dml" and "dml-lint". "dml" should be vaguely understandable by a lay-editor (since they are in a .dml file, after all) and from there they need to make the jump that dml diagnostics come from the simics modelling extension, which is still a jump (albeit a small one).

@TSonono
Copy link

TSonono commented Jun 24, 2025

Another option is dmlc for analysis and dml-lint for lint. Even though these terms might not be 100 % correct, I think they could perhaps be easier to understand for a user? It's also client agnostic

I do not think "dmlc" is an improvement over "dls". but "dml" might be? so we could use "dml" and "dml-lint". "dml" should be vaguely understandable by a lay-editor (since they are in a .dml file, after all) and from there they need to make the jump that dml diagnostics come from the simics modelling extension, which is still a jump (albeit a small one).

I'm OK with that 👍

Allows to differentiate errors from other extensions
(and between analysis and linting)

Signed-off-by: Jonatan Waern <jonatan.waern@intel.com>
Copy link

@TSonono TSonono left a comment

Choose a reason for hiding this comment

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

Thanks for adding this so quickly!

@JonatanWaern JonatanWaern merged commit 2ca67c6 into main Jun 24, 2025
4 checks passed
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