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

🍓 User Settings view #2496

Closed
Amelie-V opened this issue Mar 7, 2023 · 1 comment · Fixed by #2586 or #2593
Closed

🍓 User Settings view #2496

Amelie-V opened this issue Mar 7, 2023 · 1 comment · Fixed by #2586 or #2593
Assignees
Labels
area: ui Indicates that an issue or pull request is related to the User Interface (UI)
Milestone

Comments

@Amelie-V
Copy link
Member

Amelie-V commented Mar 7, 2023

After the dataset settings view this is the next settings view we'll tackle.
Available for OSS

Check the internal specs

@Amelie-V Amelie-V added this to the v1.5.0 milestone Mar 7, 2023
@frascuchon frascuchon modified the milestones: v1.5.0, v1.6.0 Mar 20, 2023
@Amelie-V Amelie-V assigned keithCuniah and unassigned Amelie-V and nataliaElv Mar 21, 2023
@keithCuniah
Copy link
Contributor

keithCuniah commented Mar 21, 2023

TODO:

  • create user settings page
  • create contents and header
  • create components

@keithCuniah keithCuniah added the area: ui Indicates that an issue or pull request is related to the User Interface (UI) label Mar 21, 2023
keithCuniah added a commit that referenced this issue Mar 22, 2023
# Description
Main branch for front part of user settings

Please include a summary of the changes and the related issue. Please
also include relevant motivation and context. List any dependencies that
are required for this change.

Closes [#2496](#2496) ui
part

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Refactor (change restructuring the codebase without changing
functionality)
- [ ] Improvement (change adding some improvement to an existing
functionality)
- [ ] Documentation update

**How Has This Been Tested**

(Please describe the tests that you ran to verify your changes. And
ideally, reference `tests`)

- [ ] Test A


**Checklist**

- [x] I have merged the original branch into my forked branch
- [ ] I added relevant documentation
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [ ] I made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)

---------

Co-authored-by: keithCuniah <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: leiyre <[email protected]>
Co-authored-by: frascuchon <[email protected]>
Co-authored-by: Natalia Elvira <[email protected]>
Co-authored-by: david <[email protected]>
@Amelie-V Amelie-V changed the title User Settings view 🍓 User Settings view Mar 24, 2023
frascuchon added a commit that referenced this issue Mar 28, 2023
# Description
Main branch for front part of user settings

Please include a summary of the changes and the related issue. Please
also include relevant motivation and context. List any dependencies that
are required for this change.

Closes #2496 

**Type of change**

(Please delete options that are not relevant. Remember to title the PR
according to the type of change)

- [ ] Bug fix (non-breaking change which fixes an issue)
- [x] New feature (non-breaking change which adds functionality)
- [ ] Breaking change (fix or feature that would cause existing
functionality to not work as expected)
- [ ] Refactor (change restructuring the codebase without changing
functionality)
- [ ] Improvement (change adding some improvement to an existing
functionality)
- [ ] Documentation update

**How Has This Been Tested**

(Please describe the tests that you ran to verify your changes. And
ideally, reference `tests`)

- [ ] Test A
- [ ] Test B

**Checklist**

- [x] I have merged the original branch into my forked branch
- [ ] I added relevant documentation
- [x] follows the style guidelines of this project
- [x] I did a self-review of my code
- [ ] I made corresponding changes to the documentation
- [x] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [x] I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)

---------

Co-authored-by: keithCuniah <[email protected]>
Co-authored-by: José Francisco Calvo <[email protected]>
Co-authored-by: Francisco Aranda <[email protected]>
Co-authored-by: José Francisco Calvo <[email protected]>
Co-authored-by: frascuchon <[email protected]>
Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>
Co-authored-by: leire <[email protected]>
Co-authored-by: Natalia Elvira <[email protected]>
Co-authored-by: Daniel Vila Suero <[email protected]>
Co-authored-by: David Berenstein <[email protected]>
Co-authored-by: leiyre <[email protected]>
frascuchon added a commit that referenced this issue Apr 9, 2023
##
[1.6.0](v1.6.0...v1.5.1)

### Added

- `ARGILLA_HOME_PATH` new environment variable ([#2564]).
- `ARGILLA_DATABASE_URL` new environment variable ([#2564]).
- Basic support for user roles with `admin` and `annotator` ([#2564]).
- `id`, `first_name`, `last_name`, `role`, `inserted_at` and
`updated_at` new user fields ([#2564]).
- `/api/users` new endpoint to list and create users ([#2564]).
- `/api/users/{user_id}` new endpoint to delete users ([#2564]).
- `/api/workspaces` new endpoint to list and create workspaces
([#2564]).
- `/api/workspaces/{workspace_id}/users` new endpoint to list workspace
users ([#2564]).
- `/api/workspaces/{workspace_id}/users/{user_id}` new endpoint to
create and delete workspace users ([#2564]).
- `argilla.tasks.users.migrate` new task to migrate users from old YAML
file to database ([#2564]).
- `argilla.tasks.users.create` new task to create a user ([#2564]).
- `argilla.tasks.users.create_default` new task to create a user with
default credentials ([#2564]).
- `argilla.tasks.database.migrate` new task to execute database
migrations ([#2564]).
- `release.Dockerfile` and `quickstart.Dockerfile` now creates a default
`argilladata` volume to persist data ([#2564]).
- Add user settings page. Closes
[#2496](#2496)

### Changed

- `ARGILLA_USERS_DB_FILE` environment variable now it's only used to
migrate users from YAML file to database ([#2564]).
- `full_name` user field is now deprecated and `first_name` and
`last_name` should be used instead ([#2564]).
- `password` user field now requires a minimum of `8` and a maximum of
`100` characters in size ([#2564]).
- `quickstart.Dockerfile` image default users from `team` and `argilla`
to `admin` and `annotator` including new passwords and API keys
([#2564]).
- Datasets to be managed only by users with `admin` role ([#2564]).
- The list of rules is now accessible while metrics are computed.
Closes[#2117](#2117)

### Removed

- `email` user field ([#2564]).
- `disabled` user field ([#2564]).
- Support for private workspaces ([#2564]).
- `ARGILLA_LOCAL_AUTH_DEFAULT_APIKEY` and
`ARGILLA_LOCAL_AUTH_DEFAULT_PASSWORD` environment variables. Use `python
-m argilla.tasks.users.create_default` instead ([#2564]).

[#2564]: #2564
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area: ui Indicates that an issue or pull request is related to the User Interface (UI)
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants