https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36503 --- Comment #16 from David Cook <dcook@prosentient.com.au> --- (In reply to Raphael Straub from comment #13)
In our use case having access to the domain is not necessary, but calling the hook before $patron->…->store with the domain as an additional argument could be a good idea. Then the plugin might modify $domain->update_on_auth, $domain->default_category_id or $domain->default_library_id.
The more I look at Koha::Auth::Client, the more I think the already existing approach has its flaws (like arbitrarily setting the branchcode and categorycode in the $mapped_data at the end of get_user()... I think that's probably a bug in the current implementation). -- Could you describe your use case more? I know someone who might be interested in this as well, so I'd like to get more feedback... -- You are receiving this mail because: You are watching all bug changes.