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
The adaptor-docs panel at the moment only shows documentation for the current adaptor (ie, common or http or whatever)
But soon Collections and the Collections API will be available to all adaptors.
We need to work out a way to load the collections API into the list.
The text was updated successfully, but these errors were encountered:
I suddenly wonder if there's a different concern here.
Rather than documenting collections as its own adaptor, as we do now, should we just append the collections API to every other adaptor?
A bit like how we handle common in other adaptors:
Sorry, something went wrong.
No branches or pull requests
The adaptor-docs panel at the moment only shows documentation for the current adaptor (ie, common or http or whatever)
But soon Collections and the Collections API will be available to all adaptors.
We need to work out a way to load the collections API into the list.
The text was updated successfully, but these errors were encountered: