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

number.js does not warn about incorrect section number references #80

Closed
ralfhandl opened this issue Aug 2, 2023 · 5 comments
Closed
Labels

Comments

@ralfhandl
Copy link
Contributor

ralfhandl commented Aug 2, 2023

Section number references [subsection ##SubsectionHeading] to a non-existing heading do not produce warning messages in the build script.

@ralfhandl ralfhandl added the tools label Aug 2, 2023
@HeikoTheissen
Copy link
Contributor

I get

❌ odata-csdl xml
odata-csdl/0 frontmatter.md(101): Undefined link ##SubsectionHeading

@ralfhandl
Copy link
Contributor Author

ralfhandl commented Aug 2, 2023

When I used stand-ins like [section ##1.2.3] I didn’t get warnings

@HeikoTheissen
Copy link
Contributor

When I used stand-ins like [section ##1.2.3] I didn’t get warnings

This introduces a new counter named "1" and leads to

[section 1.2.3]

@ralfhandl
Copy link
Contributor Author

Is that a bug or a feature? When would I use this feature?

I found the current behaviour surprising, and would have preferred a warning in the log.

If you want to keep it how it works now, just close this issue.

Thanks in advance!

@HeikoTheissen
Copy link
Contributor

Is that a bug or a feature? When would I use this feature?

It is a feature that links are generated by ##someabbrev and referenced by [... ##someabbrev]. But I have now allowed dots in abbrev so that [section ##1.2.3] gives a warning.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants