Skip to content
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

Support private uploads #5

Merged
merged 2 commits into from
Feb 29, 2024
Merged

Support private uploads #5

merged 2 commits into from
Feb 29, 2024

Conversation

cnweaver
Copy link
Collaborator

Implements #4 .
Depends on scimma/scimma-admin#67 .

C. Weaver added 2 commits January 31, 2024 16:58
Sanity-check the structure of hop_auth responses more carefully.
@cnweaver cnweaver added the enhancement New feature or request label Feb 12, 2024
@cnweaver cnweaver self-assigned this Feb 12, 2024
@cnweaver cnweaver marked this pull request as ready for review February 15, 2024 19:09
@cnweaver cnweaver requested a review from jnation3406 February 15, 2024 19:09
Copy link

@jnation3406 jnation3406 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine, but my preference would be to just create an endpoint in scimma-admin to get the information you want in a single request, rather than use a multi-request to make two requests fast. It looks like here your trying to get the permissions and details of a topic? That seems reasonable to expose all together in an endpoint to me...

@cnweaver
Copy link
Collaborator Author

The two things being queried here are not very closely related; one is the properties of the topic itself and the other are the permissions the current user has with respect to that topic. I think it's indicative that these are in completely separate database tables, internally, so while it would be possible to make one route that returned both, I would struggle to figure out what it should even be named, as it wouldn't have a single, well-defined purpose, where the existing routes are, to the extent possible, designed to be orthogonal and independent.

@cnweaver
Copy link
Collaborator Author

Thinking about this a bit more it occurs to me to describe it as: The REST API needs to support all relevant 'fundamental' operations, and the multi-request is exactly a general purpose system to allow composition of any combination of those, instead of having to hard-code each combination that we discover is relevant when we want it.

@cnweaver cnweaver merged commit 76b53a2 into master Feb 29, 2024
@cnweaver cnweaver deleted the private-uploads branch February 29, 2024 16:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants