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

Formatting issue in daily build? #126

Closed
jonblower opened this issue Aug 12, 2022 · 6 comments
Closed

Formatting issue in daily build? #126

jonblower opened this issue Aug 12, 2022 · 6 comments

Comments

@jonblower
Copy link
Contributor

jonblower commented Aug 12, 2022

In the "Examples" section of the daily build (section 10.6.1.3), is there an issue with the hyperlink syntax? The text appears as follows:

Example of a domain object with ["Grid"][domain-types] domain type:

I assume the "Grid" text is meant to hyperlink to the domain types section?

@edzer
Copy link

edzer commented Aug 16, 2022

The also cookbook contains several references to https://covjson.org/domain-types/ , but that does not exist - I guess this is the same issue.

@jonblower
Copy link
Contributor Author

Ooh, it looks like that link has got broken, thanks for pointing that out. @letmaik I guess we'll have to edit the cookbook text?

@letmaik
Copy link
Contributor

letmaik commented Aug 16, 2022

See covjson/cookbook#3 for the cookbook issue. Let's keep this one for spec formatting problems.

@chris-little
Copy link
Contributor

@ghobona This is another formatting issue with the CoverageJSON spec that we do not understand and need guidance please.

@chris-little
Copy link
Contributor

@ghobona @jonblower @letmaik This example and several others now fixed by PR #142

@chris-little
Copy link
Contributor

@jonblower @letmaik Anchors and link formatting now fixed by PR #137 and #142. Please note the spec text has a section common_domain_types, not domain-types.

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

No branches or pull requests

4 participants