Skip to content

feat: allow accounts with a quota of 0 GiB #17413

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

Merged
merged 13 commits into from
Apr 7, 2025

Conversation

rubenhensen
Copy link
Contributor

Description

Previously, setting your quota to 0 would make it unlimited. This change makes 0 a possible value, while leaving the field empty/null sets its to unlimited.

This change makes it possible to have no-upload accounts.

How Has This Been Tested?

  • Create account, set quota to 0, try to upload a photo.

Screenshots (if appropriate)

Screenshot from 2025-04-06 00-12-48

Checklist:

  • I have performed a self-review of my own code
  • I have made corresponding changes to the documentation if applicable
  • I have no unrelated changes in the PR.
  • I have confirmed that any new dependencies are strictly necessary.
  • I have written tests for new code (if applicable)
  • I have followed naming conventions/patterns in the surrounding code
  • All code in src/services/ uses repositories implementations for database calls, filesystem operations, etc.
  • All code in src/repositories/ is pretty basic/simple and does not have any immich specific logic (that belongs in src/services/)

@alextran1502 alextran1502 changed the title Allow accounts with a quota of 0 GiB feat: allow accounts with a quota of 0 GiB Apr 6, 2025
@alextran1502
Copy link
Contributor

FYI, for translation, you only need to provide the en.json content.

@danieldietzler
Copy link
Member

Also, please fix the failing tests. Thanks :)

@github-actions github-actions bot added the documentation Improvements or additions to documentation label Apr 6, 2025
@rubenhensen
Copy link
Contributor Author

I think I fixed all the tests.

@rubenhensen
Copy link
Contributor Author

rubenhensen commented Apr 6, 2025

Okay the e2e tests are throwing me a bit for a loop. I do not know why all these tests are failing, they seem to have nothing to do with what I changed. Could it be the open-api/immich-openapi-specs.json? I never used this way of creating an api so it might be giving some issues in a way I do not understand yet.

Copy link
Member

@danieldietzler danieldietzler left a comment

Choose a reason for hiding this comment

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

The code looks very good to me, thanks! You can disregard the failing test, that wasn't your fault :)

@alextran1502 alextran1502 merged commit 99cddf1 into immich-app:main Apr 7, 2025
40 checks passed
midzelis pushed a commit that referenced this pull request Apr 10, 2025
* Allow 0GiB quotas in user create/edit form, remove unused translations

* Make requireQuota check for null or 0

* Add unlimited quota change to the docs

* Fix user dto formatting

* Fix formating edit-user-form

* Regenerate open-api files

* Revert unnecessary i18n file changes

* Re-add newline en.json

* Resolve linting issues

* Fix formatting edit-user-form

* Re-add manifest
savely-krasovsky pushed a commit to savely-krasovsky/immich that referenced this pull request Jun 8, 2025
* Allow 0GiB quotas in user create/edit form, remove unused translations

* Make requireQuota check for null or 0

* Add unlimited quota change to the docs

* Fix user dto formatting

* Fix formating edit-user-form

* Regenerate open-api files

* Revert unnecessary i18n file changes

* Re-add newline en.json

* Resolve linting issues

* Fix formatting edit-user-form

* Re-add manifest
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants