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
Routes for active? archived? all?
Do we want the logic in the backend?
Also for nested routes - do we want to have a route that accesses all active tickets/notes and not have them associated with a specific resource?
The text was updated successfully, but these errors were encountered:
We decided to have an archive endpoint in the future!
Sorry, something went wrong.
ryandbarnett
stiehlrod
KStockton
carriewalsh
No branches or pull requests
Routes for active? archived? all?
Do we want the logic in the backend?
Also for nested routes - do we want to have a route that accesses all active tickets/notes and not have them associated with a specific resource?
The text was updated successfully, but these errors were encountered: