mirror of
https://github.com/BookStackApp/BookStack.git
synced 2026-02-05 16:49:47 +03:00
Bulk API support in BookStack #1791
Reference in New Issue
Block a user
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?
Originally created by @suvreal on GitHub (Jul 13, 2020).
I would like to ask if there already is or would actually be availability of bulk API support to CRUD the data in BookStack. I don't know if it is matter of upcoming updates.
I am sorry for making possible duplicate of ticket.
--Suvreal
@watschi commented on GitHub (Jul 13, 2020):
You opened the same issue 6 days ago in #2176
Dan, the maintainer of this project, already answered that this will be available in future updates.
If you're not sure if there's already an open issue requesting a feature you would like to see, you can use the search function on the issue list.
@suvreal commented on GitHub (Jul 13, 2020):
My apologies. I thought that the initial thought of adding bulk API handle was not said in previous ticket. In the previous ticket there was said bulk import/export accordig to the user UI, so I felt importance of asking API bulk in separate ticket. Again, sorry for possible mess.
@watschi commented on GitHub (Jul 13, 2020):
No worries, but please remember that maintaining an open source project is a lot of (unpaid) work and more issues/requests equals less time available to actually develop the application.
I'm sure the maintainers are happy about constructive feedback and bug reports, but duplicate requests without much effort or research put into them might discourage people from continuing working on great projects ;)
I think this issue can be closed, since API developement ist already tracked at #1852 and #823, bulk import/export at #43 and an example script for bulk exports is provided at #1979
@suvreal commented on GitHub (Jul 13, 2020):
I just want to provide constructive feedback, I am sorry if it might be understood other way (by my communication actually). I thought that this idea was not contained in previous ticket, because of which this ticket might be considered as duplicate. I will pay more attention to my communication to prevent to anything like this :).
I agree, we can close it.