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.

Sign up for GitHub

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

Jump to bottom

BE: Nuke Messages v1 API #211

Open
Haarolean opened this issue Mar 15, 2024 · 1 comment · May be fixed by #633
Open

BE: Nuke Messages v1 API #211

Haarolean opened this issue Mar 15, 2024 · 1 comment · May be fixed by #633
Assignees
@Haarolean
Labels
area/messages good first issue Up for grabs hacktoberfest Issues good for hacktoberfest goal scope/backend Related to backend changes scope/frontend Related to frontend changes status/pending-backend status/triage/completed Automatic triage completed type/chore Boring stuff, could be refactoring or tech debt

Comments

@Haarolean
Copy link
Member

Haarolean commented Mar 15, 2024 •
edited
Loading

Ship after August 2024

After #47 is merged in the next release we can drop legacy v1 API

  1. BE: Drop messages v1 API (contracts) (only GET)
  2. BE: Rename /v2 endpoint, remove suffix
  3. Update the URL on FE
  4. Fix BE/FE tests
@Haarolean Haarolean added good first issue Up for grabs scope/frontend Related to frontend changes scope/backend Related to backend changes type/chore Boring stuff, could be refactoring or tech debt labels Mar 15, 2024
@Haarolean Haarolean added this to the 1.1 milestone Mar 15, 2024
@kapybro kapybro bot added status/triage Issues pending maintainers triage area/messages status/triage/completed Automatic triage completed and removed status/triage Issues pending maintainers triage labels Mar 15, 2024
@Haarolean Haarolean moved this to Beginner in Up for grabs Mar 15, 2024
@Haarolean Haarolean moved this from In Development to Todo in Up for grabs Mar 16, 2024
@Haarolean Haarolean removed this from Release 1.1 Apr 3, 2024
@Haarolean Haarolean removed this from the 1.1 milestone Apr 3, 2024
@Haarolean Haarolean moved this to Backlog in Housekeeping Apr 27, 2024
@Haarolean Haarolean removed this from Housekeeping Apr 27, 2024
@Haarolean Haarolean added the hacktoberfest Issues good for hacktoberfest goal label Oct 4, 2024
@Haarolean Haarolean self-assigned this Oct 24, 2024
@Haarolean Haarolean moved this from Todo to In Development in Up for grabs Oct 24, 2024
@Haarolean Haarolean linked a pull request Oct 24, 2024 that will close this issue
Draft
13 tasks
@Haarolean Haarolean moved this from In Development to In Review in Up for grabs Oct 24, 2024
@Haarolean
Copy link
Member Author

Frontend changes in #633 required

@Haarolean Haarolean moved this from In Review to In Development in Up for grabs Dec 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Haarolean Haarolean

Labels
area/messages good first issue Up for grabs hacktoberfest Issues good for hacktoberfest goal scope/backend Related to backend changes scope/frontend Related to frontend changes status/pending-backend status/triage/completed Automatic triage completed type/chore Boring stuff, could be refactoring or tech debt
Projects
Up for grabs
Status: In Development
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

BE: Chore: Drop messages v1 kafbat/kafka-ui
1 participant
@Haarolean