https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38446
--- Comment #19 from Jonathan Druart <[email protected]> --- (In reply to Pedro Amorim from comment #14) > (In reply to Jonathan Druart from comment #7) > > I don't this this is correct. > > > > We need a separate route to retrieve the ERM's attributes. Or should it be > > in /erm/config? > > > > IMO we don't want to give access to the attributes of other modules if the > > permissions is not set. > > I sort of agree with this but having to have a specific endpoint for every > new resource that adopts extended attributes would be a bit overkill? I personally don't think it's overkill, and I still think it's what we should do. eg. /erm/additional_fields > How about just put 'catalogue' : 1 as permission, and handle the permissions > logic in the REST controller itself? Yes, that's another possible option. /additional_fields would return all the fields depending on the user's permissions. It will be easier to integrate with the changes made by bug 38201 (and the RelationshipTableDisplay.vue component). -- 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/
