https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=38941
--- Comment #26 from Matt Blenkinsop <[email protected]> --- > That said, can you explain things more? In the case of acquisitions menu, it > looks like you do have access to the pinia stores, but that it's just not > being populated? It also looks like it gets mounted as a single component > Vue app in the end? Looking at bug 38930, it looks like the permissionsStore > is not used anywhere currently? There's the ERM example which shows an > ERM-specific implementation for using the permissionsStore, but that seems > suboptimal. > > When I first heard of bug 38930, I thought it was going to introduce a core > API endpoint for fetching current user details and then put the permissions > in the permissionsStore for use by Vue components. Even outside of Vue, I > reckon having an API endpoint to fetch that information would be useful. Its currently being used by the Vendors Vue module - when the acquisitions menu is loaded as part of the vendors vue app we have access to the permissions store as it is populated by the module's config endpoint and the menu is just used as a generic vue component rather than a custom element. When it is used as a custom element, the permissionsStore is technically available but isn't populated as there is no specific vue app with a config endpoint to populate from. A future enhancement could certainly be to update the permissions store to self-populate and remove the need for the TT variables -- 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/
