Implement Selfoss API 5.0.0 #71
Labels
No Label
Difficulty - Beginner friendly
Difficulty = Easy
Difficulty = Hard
Difficulty = Medium
Priority = CRITICAL
Priority = High
Priority = Low
Priority = Normal
Priority = Some day
Status - Fixed somewhere else
Status - No details provided
Status = Can't fix
Status = Duplicate
Status = Help wanted
Status = Invalid
Status = Need more details
Status = Taken
Status = Wontfix
Type - Selfoss works like this
Type = Bug
Type = Chore
Type = Enhancement
Type = Feature
Type = Question
Type = SELFOSS API ISSUE
Type = Tools
Type = UX/Design
Up For Grabs
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: Louvorg/ReaderForSelfoss-multiplatform#71
Loading…
Reference in New Issue
Block a user
No description provided.
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?
Selfoss 2.19 will have a new api version (https://github.com/fossar/selfoss/pull/1360).
As far as I can see, the application should work seamlessly with most of these changes but we should add a couple of tests to make sure that everything works correctly.
Changes are:
Get /login
is deprecated andPOST /login
will have to be used; this is already planned in #53 and should be backward compatible with all api versions. This is a breaking change.POST /source/delete/:id
is deprecated in favour ofDELETE /source/:id
, the latter is what is already being used in the applicationGET /logout
is deprecated in favour of the newDELETE /api/session/current
this function is not currently in use by the application but should be implemented to close #53 taking into account the different handling according to api version.POST /source/update
andPOST /source/:id/update
now return a 403 error upon failed authentication; this should already be correctly handled by the application.I checked it now,
DELETE /source/:id
andGET /update
work correctly with the current implementation.The three first points are done.
The last one will be in #99.