Skip to content
This repository has been archived by the owner on Jun 14, 2024. It is now read-only.

[TASK] Migrate POST /api/workspaces endpoin to POST /api/v1/workspaces #149

Closed
Tracked by #4773
jfcalvo opened this issue May 7, 2024 · 0 comments · Fixed by #150
Closed
Tracked by #4773

[TASK] Migrate POST /api/workspaces endpoin to POST /api/v1/workspaces #149

jfcalvo opened this issue May 7, 2024 · 0 comments · Fixed by #150
Assignees

Comments

@jfcalvo
Copy link
Member

jfcalvo commented May 7, 2024

No description provided.

@jfcalvo jfcalvo self-assigned this May 7, 2024
@jfcalvo jfcalvo transferred this issue from argilla-io/argilla May 7, 2024
@jfcalvo jfcalvo linked a pull request May 7, 2024 that will close this issue
15 tasks
jfcalvo added a commit that referenced this issue May 13, 2024
…aces` (#150)

# Description

This PR adds a new endpoint `POST /api/v1/workspace` allowing the
creation of new workspaces for API v1.

Changes of the new endpoint compared to the old one:
* The new endpoint returns a `201` status code instead of the `200`
returned by the old endpoint.

I have added also some changes to the new token creation endpoint to
return `201` instead of `200`.

Closes #149

**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**

- [x] Adding new tests and manually checking the old ones pass with the
new endpoint.

**Checklist**

- [ ] I added relevant documentation
- [ ] follows the style guidelines of this project
- [ ] I did a self-review of my code
- [ ] I made corresponding changes to the documentation
- [ ] My changes generate no new warnings
- [ ] I have added tests that prove my fix is effective or that my
feature works
- [ ] I filled out [the contributor form](https://tally.so/r/n9XrxK)
(see text above)
- [ ] I have added relevant notes to the CHANGELOG.md file (See
https://keepachangelog.com/)
@jfcalvo jfcalvo closed this as completed May 13, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant