553 Support v1 and v2 URLs in AppD spec #666
Conversation
…andard version of spec
kriswest
changed the base branch from
master
to
Appd-consolidated-update-branch
|
@ggeorgievx FYI I'm targetting this PR at a branch so that we can collect up a number of changes to present to the SWG as a consolidated set (rather that 20 different PRs). Other rounds of changes from discussion groups have devolved into a nightmare of conflict resolutions (each merge created conflicts in all the remaining PRs) which I think we need to avoid this time ;-) particularly as I'm about to start on the spec re-org PR (#491) which will conflict with everything. |
|
@ggeorgievx I'm going to go ahead and merge this into the consolidated branch as I need to base other PRs on it. Once done I'll raise a new WIP PR for the consolidated branch to enable review and tag you in that |
There was a problem hiding this comment.
Everything looks great @kriswest 🙌
I will look into the version (1.2 vs next) issue on the AppD part of the website.
|
Good luck - I thought it might be todo with the fact the appD page wasn't an HTML fragment (see website/pages/schemas/next/app-directory.html) as expected by the wrapPagesHtml option (was producing HTML with two html/head/body tags) but that wasn't it. Hence, I suspect its just a bug in docusaurus... it can be manually fixed in the generated HTML post-deployment (the version number is generated into the HTML not set by a script of anything similar) |
resolves #553
Moves latest work on appD to /v2/ urls and restores /v1/ urls to 1.2 standard version of spec.
Will enable an appD implementation to serve both formats (if desired) to simplify migration.
Change agreed at meeting: