You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
PR #437 (issue #314) introduced a breaking change to the App Directory specification, namely changes to the Application schema. This issue suggests adding backwards compatibility to the specification by using the versioned URL end-points:
Introduce v2 end-points for all newly added changes
Add back the old Application schema and sort out any component naming issues
Mark the v1 end-points as optional/deprecated
The text was updated successfully, but these errors were encountered:
I agree with this approach - we opted for the next version to be a major release in order to introduce breaking changes to the appD, but it makes sense to use the versioned URLs to make transitions easier and to keep the URLs aligned with the major version number.
PR #437 (issue #314) introduced a breaking change to the App Directory specification, namely changes to the
Application
schema. This issue suggests adding backwards compatibility to the specification by using the versioned URL end-points:v2
end-points for all newly added changesv1
end-points as optional/deprecatedThe text was updated successfully, but these errors were encountered: