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
The API playground is directly linked to whatever the spec is on master. This is an issue as users will use the release tag and presumably use the playground link to explore the API, as the raw spec text is difficult to navigate.
However, the link is always to a single playground link, which currently tracks master.
I'm unsure how the playground works exactly, but ideally every commit would link to its specific version's implementation. If this is not possible, then at least the release versions should link to a correct playground.
The text was updated successfully, but these errors were encountered:
The API playground is directly linked to whatever the spec is on
master
. This is an issue as users will use the release tag and presumably use the playground link to explore the API, as the raw spec text is difficult to navigate.However, the link is always to a single playground link, which currently tracks
master
.I'm unsure how the playground works exactly, but ideally every commit would link to its specific version's implementation. If this is not possible, then at least the release versions should link to a correct playground.
The text was updated successfully, but these errors were encountered: