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

Support for emitting custom warnings #1322

Open
ondohotola opened this issue May 25, 2023 · 1 comment
Open

Support for emitting custom warnings #1322

ondohotola opened this issue May 25, 2023 · 1 comment
Labels
diagnostics Improvements to compiler errors feature request New feature or request

Comments

@ondohotola
Copy link

Description

In issue #1276 @Enivex proposed a very helpful solution for missing references.

However, I noticed that that will happily generate (?) (which I have adapted to ?? without reporting this, which means you may end up with orphan references.

I have not been able to find a way to make typst squeal so I can adapt the #show raw rule's missing condition.

Use Case

There should be other conditions where a warning type message triggered programatically might be helpful.

@ondohotola ondohotola added the feature request New feature or request label May 25, 2023
@laurmaedje
Copy link
Member

Related: #600

@Enivex Enivex added the diagnostics Improvements to compiler errors label May 25, 2023
@laurmaedje laurmaedje changed the title How to emit a "warning" of sorts when compiling a document? Support for emitting custom warnings Nov 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
diagnostics Improvements to compiler errors feature request New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants