Closed tobie closed 1 year ago
Something's off unfortunately. How urgent is this?
No rush, I just happened to notice it in a spec today, so raised the issue before I forgot.
@tobie, I made some suggestions which I believe should work. I see specref still relies on tr.rdf which we plan to retire in the future. Indeed, tr.rdf has some limitations and doesn't show data related to the specification series. Instead, the W3C API provides more details, e.g. https://api.w3.org/specification-series/png.
That said, I'm aware upgrading specref to use the API isn't a priority but I'm just mentioning in case we can find someone to work on that.
Thanks @deniak. Your changes would be overwritten on next update, unfortunately.
Thanks @deniak. Your changes would be overwritten on next update, unfortunately.
Right, I forgot the references get automatically updated.
Changing the newId
for PNG
in overwrites/w3c.json
should do the trick I guess:
{ "id": "PNG", "action": "renameTo", "newId": "PNG-1"},
{ "id": "PNG", "action": "createAlias", "aliasOf": "png-3"}
Have you tried it? It wasn’t working for me yesterday.
Have you tried it? It wasn’t working for me yesterday.
I just gave it a try and it seems to work. I don't have write access to the repo, but I'm happy to open a new PR if you want.
Adding your changes here would be easier.
Adding your changes here would be easier.
Done.
Sorry, I hadn't thought this through much and didn't consider you'd have to force push to clean things up. Apologies!
no worries :)
Thanks @tobie
No, thank you!
Closes #758
/cc @svgeesus
I think this is what you're asking for. Leverages an undocumented (sorry) feature to force overwrites for exactly those usecases.