We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
in relation to
I wondered if we could/should sophisticate non-webdav HTML "frontend" to serve API URLs if detecting chrome, safari, etc human browsers.
Since "implicit" is evil, an alternative could be to add to web frontend a checkbox:
so it would be for a user to decide between the two. For the sake of dandi/dandi-cli#1572 we could document to "click" there to get API urls.
The text was updated successfully, but these errors were encountered:
@yarikoptic I don't like any part of this suggestion.
Sorry, something went wrong.
No branches or pull requests
in relation to
I wondered if we could/should sophisticate non-webdav HTML "frontend" to serve API URLs if detecting chrome, safari, etc human browsers.
Since "implicit" is evil, an alternative could be to add to web frontend a checkbox:
so it would be for a user to decide between the two. For the sake of dandi/dandi-cli#1572 we could document to "click" there to get API urls.
The text was updated successfully, but these errors were encountered: