https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=29523
--- Comment #170 from Martin Renvoize <[email protected]> --- Hmmm.. I hadn't really tested public and accessible together. The real use case for the accessible stuff here is staff side where a staff user can expect the same overall representation for all objects that exist but they amy not have the right to see all the data. Whereas 'public' is about thrid party facing api's where they will never see some of the fields at all so the object representation is actually different. 'Public' removes fields outright.. and really should have it's own schema's. 'Accessible' redacts the values of fields, but leaves the keys present so the object itself is a consistent representation. No.. for your errors in particular. 'Expected string - got null' - If this were a staff side request I'd say that highlights an issue in our schema.. with this patch, the majority of fields should actually be 'type or null' in the schema's. For the public side, I'm less sure. -- 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/
