https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=39199 --- Comment #10 from David Cook <dcook@prosentient.com.au> --- (In reply to Shi Yao Wang from comment #9)
(In reply to David Cook from comment #8)
@Shi Yao Wang, is your intention here to just allow an API user to view and send emails arbitrarily? I don't think there's a scenario where that's going to be a good idea. If you have a more specific scenario, I'd be happy to provide some advice.
Actually my initial intention was to just implement a GET route for notices to display similarly to koha/members/notices.pl
This bug was the closest thing I could find and I thought adding a POST route as well wasn't too complicated.
Should I open a separate bug for the GET route only?
Possibly yeah. Could you describe your use case more? It sounds to me that you're after something more like "GET /patrons/{patron_id}/notices" for an API endpoint? So the file would be api/v1/swagger/paths/patrons_notices.yaml. You'll have to remember to honour things like Library Groups (so using something like Koha::Patrons->search_limited(). We have to make sure that API endpoints mimic the behaviour of the .pl controllers. Of course, that's easier said than done for a lot of API scenarios... but yeah describe it a bit more. -- You are receiving this mail because: You are watching all bug changes.