-
Notifications
You must be signed in to change notification settings - Fork 5
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
Allow a person to tag buckets. #419
Conversation
then we need a better selector for that switch, or something is off with clicking the parent |
7687ed5
to
fa6bdea
Compare
fa6bdea
to
373a80a
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Some small alterations to the Finnish upon further inspection, other than that LGTM.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the new POST endpoint "/api/bucket/meta" should be added to the API.yaml
373a80a
to
0d8239f
Compare
This feature has a frontend and backend part. From the frontend, user can create tags at the create bucket screen. On the backend, the tags are stored as metadata in the swift object store.
0d8239f
to
406edff
Compare
Added entry to API docs
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
This is a continuation to the tagging buckets feature from PR #419. The openApi spec supports tuples in 3.1 with prefixItems. We may want to change the api docs when that comes into use.
Description
Gives a person the possibility to add or remove tags from a bucket. Includes the ability to show or hide tags when browsing the buckets.
Please, check the Finnish language :)
Related issues
Related to #85.
Type of change
Changes Made
Added backend for updating metadata for a bucket. Added UI for displaying tags for containers, as well as hiding them. There is a new button, called 'Edit', which makes it possible to edit a bucket's tags. When creating a new Bucket, it's possible to add tags to it.
Tags are not displayed in the bucket view (after double click on a bucket). There's no edit button on that page either.
Testing
Mentions
Thanks to @sampsapenna for solving my javascript sync/async mess.