reuse/api
9
3
Fork 2
Code Issues 38 Pull Requests 1 Activity

Implement CRUD #116

New Issue
Open
opened 2025-10-17 13:26:27 +00:00 by fkobi · 0 comments
fkobi commented 2025-10-17 13:26:27 +00:00
Owner
Copy Link
Copy Source

As of right now:

  • forms Create entries in repos.json file
  • reuse-api Reads the entries in repos.json file and derives it's database from it(#122)

We lack the capability to Update and Remove data.
That is a pretty big issue in my opinion as we do not support the 4 basic operations of persistent storage.

As of right now: - `forms` Create entries in `repos.json` file - `reuse-api` Reads the entries in `repos.json` file and derives it's database from it(https://git.fsfe.org/reuse/api/issues/122) We lack the capability to Update and Remove data. That is a pretty big issue in my opinion as we do not support the 4 basic operations of persistent storage.
fkobi added the
component
database
 label 2025-11-14 09:38:54 +00:00
fkobi added the
prio
high
 label 2025-11-14 09:49:28 +00:00
fkobi added a new dependency 2025-11-14 10:06:54 +00:00
#123 `repos.json` is read-only
fkobi added a new dependency 2025-11-14 10:07:11 +00:00
#122 Database is derived from `repos.json`
fkobi added this to the 2.0 -- A thought-out backend redesign milestone 2025-11-14 10:18:48 +00:00
fkobi self-assigned this 2025-11-14 10:18:52 +00:00
fkobi added a new dependency 2025-11-14 12:46:35 +00:00
#124 Use a database solution that makes sense
fkobi added the enhancement label 2025-12-17 11:36:08 +00:00
fkobi added the bug label 2025-12-17 11:41:28 +00:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
1.0
Problems that do not concern the 2.0 rewrite, probably should be ignored
component
backend
Issues concerning the backend (logic connecting frontend with the database)
component
database
Issues concerning the database
component
docs
Issues regarding documentation
component
frontend
Issues concerning the frontend
prio
high
High priority
prio
low
Low priority
prio
maybe
Lowest priority
prio
mid
Medium priority
bug
Something is not working
 duplicate
This issue or pull request already exists
 enhancement
New feature
 help wanted
Need some help
 invalid
Something is wrong
 question
More information is needed
 wontfix
This won't be fixed
No Label
component
database
prio
high
 bug enhancement
Milestone
No items
No Milestone 2.0 -- A thought-out backend redesign
Assignees
Clear assignees
carmenbianca (carmenbianca) fkobi (Filip Kobierski) florian.vuillemot (florian.vuillemot) floriansnow (Florian Snow) git-robot linus (Linus Sehn) max.mehl (Max Mehl) nico.rikken (nico.rikken) reinhard (Reinhard Müller) renovate-bot (Renovate Bot) tobiasd (tobiasd)
No Assignees fkobi
1 Participants
Notifications
Due Date
No due date set.
Depends on
#122 Database is derived from `repos.json`
reuse/api
#123 `repos.json` is read-only
reuse/api
#124 Use a database solution that makes sense
reuse/api
Reference: reuse/api#116
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?