-
Notifications
You must be signed in to change notification settings - Fork 10
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
List of Capabilities is inconsistent with example #164
Labels
documentation
Improvements or additions to documentation
Comments
johnbrvc
added a commit
that referenced
this issue
Nov 13, 2023
One of the examples for the Access endpoint showed a capability of "patch_time". This capability does not appear in the Capabilities list that says "All capabilities are listed in the table below". Clearly, "patch_time" is not in the list. It makes sense to change the example to use a documented property and "contest_start" makes the most sense here.
Just to be clear, any system can support capabilities that are not in the spec (like additional objects, this is one of the expected places for systems to extend or try new things for future spec versions), but I 100% agree that our examples should use capabilities that are in the spec. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The
/contests/contestid/access
endpoint description has an example that shows a capability (patch_time
) that is not part of the Capabilities list, rather, thecontest_start
capability is what should probably be used in the example, eg:The text was updated successfully, but these errors were encountered: