feat: Add basic storage limit request functionality #1398
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
e-schneid
force-pushed
the
feature/e-schneid/user-requests
branch
from
30c480a to
6781ab2
Compare
e-schneid
force-pushed
the
feature/e-schneid/user-requests
branch
from
6781ab2 to
f33a296
Compare
e-schneid
force-pushed
the
feature/e-schneid/user-requests
branch
2 times, most recently
from
2a80e11 to
75fb1a6
Compare
jsdevel
force-pushed
the
feature/e-schneid/user-requests
branch
from
75fb1a6 to
a55713d
Compare
jsdevel
approved these changes
Jun 16, 2022
This was referenced Jun 16, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently to request a storage limit change, the user will click a mailto link and compose an email describing why they deserve to be granted the additional storage. This PR adds an API call to store this request in our database which can then be approved/declined via the admin application.
This is currently very basic. We would like to flesh this out so that the user can store a reason (or examples, links, etc) for why they should be approved and avoid having the user compose emails altogether (this is already supported in the admin application and in the database), but additional UX needs to be worked through and also perhaps some mailing infrastructure as well (so that we can, for example, send a daily email that aggregates any new requests that were made in the previous day).