https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=28157
--- Comment #15 from David Cook <[email protected]> --- Actually, after reviewing the patches again, I think that I get the idea. With an interactive session, we're logging in with username, password, and target branch. However, with an API session, we're logging in using only username and password, so we don't really have any way of providing a branch. So unless we require people to switch branches using an API endpoint first, the only other option is to provide that x-koha-library header or I suppose embed the library ID in the route like you've suggested. I suppose an alternative would be to pass the target branch in parameters but that would only work for certain endpoints. Hmm feels too abstract at the moment for me to really think of concrete examples. But I suppose the patch is already pushed so it doesn't really matter anymore heh. -- You are receiving this mail because: You are watching all bug changes. _______________________________________________ Koha-bugs mailing list [email protected] https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-bugs website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
