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
ReSpec should warn on unstructured/text specref entries #1082
Comments
How odd... having a quick look. |
I'm not able to reproduce locally, so will need to dig a little deeper. However, the "nanotabs" script is generating errors which maybe related. First error:
Sent a PR. Let's check again once that goes in. |
Ok...I've removed the nanotabs script (as we don't use it anymore). |
Ok, thanks for eliminating that.
Local biblio is empty. Still trying to see where else that reference is getting lost and why. |
(as a temporary fix, adding it to localBiblio might fix it :) ) |
Ok, will add the following to spec ref.
|
here's an update:
|
@riannella thanks! Will add those now. |
@riannella sent PR... just need @tobie to help me with something there: For other legacy entries, you can use this tool to generate them: |
Anyway, that should fix the entries... I'll update ReSpec to warn when a legacy entry type is encountered to encourage authors to update those. |
great, thanks for your help @marcoscaceres |
@riannella, after we merge, you will need to do a "hard reload" of the spec in the browser to get the broken entries to show up - otherwise, they should fix themselves after 24 hours (I make ReSpec refresh the spec's database once a day - or when it detects things have been updated on the server - in the background). |
Yeah..thanks...Now to get the title listed first #857 👍 |
agree... what's there is pretty terrible. Might just fix that without doing the custom styles. |
For some strange reason, 2 references are not working in our document:
http://w3c.github.io/poe/vocab/#informative-references
They are [[iso3166]] and [[iso8601]]
And I tried "ISO" as well..
any ideas?
The text was updated successfully, but these errors were encountered: