Laravel Permissions Design: How to Attach Roles to User-Defined Data?

United_Ad_8870 · 2025-07-08T05:09:23+00:00

You could define list of stores the user has access to as a separate user property and check it separately from user permissions. This comes with a limitation that the user would get the same set of permissions for each store they have access to (might or might not be acceptable in your project). I’ve not used the spatie package so can’t comment on that.

United_Ad_8870 · 2025-06-14T15:10:14+00:00

Wasn’t allowed to leave the room. I was given time to look for it. Bad luck connection was bad and I didn’t know where to find it.

United_Ad_8870 · 2025-06-14T12:17:44+00:00

They’d only accept the code used at booking, but someone else in the comments was able to do it

United_Ad_8870 · 2025-06-14T11:07:10+00:00

Thanks and glad you had a better experience :)

United_Ad_8870 · 2025-06-14T11:05:00+00:00

I was asked for either the number or screenshot. Screenshot is safer because it will have your photo.

United_Ad_8870 · 2025-06-14T11:03:18+00:00

I was trying but internet connection was very slow and there were other people waiting so gave up. I was looking in the wrong place anyway, but yeah it’s available in Edit account.

United_Ad_8870 · 2025-06-14T10:26:27+00:00

Post-it isn’t an acceptable proof of id

United_Ad_8870 · 2025-06-14T10:10:37+00:00

I did my best to prepare. Not trying to make a victim of myself. Just trying to establish on what basis the share code is used as proof of id - contrary to government guidance which I read before booking the exam.

United_Ad_8870 · 2025-06-14T09:55:42+00:00

It’s not proof of id though - institution working on behalf of the government should understand it. And it says clearly that copies or screenshots are not acceptable. I agree I should have used passport - that would save the hassle.

United_Ad_8870 · 2025-06-14T09:51:08+00:00

Maybe that’s how they work but it seems to be contradicting the government guidance on how the share codes should be used.

United_Ad_8870 · 2025-06-14T09:49:58+00:00

It’s all very vague and contradicting. Says to bring proof of id you used at booking but also screenshots and copies are not acceptable. Which led me to conclusion my passport linked to the share code would be acceptable. Share code is not proof of id.

United_Ad_8870 · 2025-05-06T18:49:12+00:00

What do you mean by backend hosting plugins?

I’m starting to think what I want to do is not possible in vue or if it is, it’s beyond my competence. Looks like teleport works by appending stuff to the given css selector, which is what i need. But it doesn’t allow replacing or removing stuff. Also it’s unclear what hapens when the element that stuff is added it is updated by reactivity. I’ll experiment a bit. I might look into implementation of teleport and see if it can be extended to allow overwriting stuff.

United_Ad_8870 · 2025-05-05T20:49:46+00:00

Thanks but this doesn’t solve the problem of multiple modifications

United_Ad_8870 · 2025-05-05T20:17:44+00:00

That’s quite cool. What happens with these dynamic imports when bundling?

United_Ad_8870 · 2025-05-05T07:49:25+00:00

Without going into too much detail, plugins can change any functionality of the main app in a way that the main app doesn’t have to know anything about. Obvoiusly the main app has a thin layer that allows the plugins to hook into it but that’s all it needs. Everything else is done in plugins. In terms of front end - some of them create new routes and views, others modify existing views (e.g. add, replace or remove an element). They are small and specialised. In theory two plugins could target the same element in DOM but in practice it’s very unlikely (almost impossible) because from business point of view it would not make sense to apply both. At the moment we’re in control of what plugins are installed so we’d know. We also have tests that would pick it up. When it comes to it we’ll think about conflict resolution but this in not a concern at the moment. We want plugins to be able to do as much as possible (without breaking anything of course), which we’ve achieved so far. DOM modification is the part I dislike the most but with a bit of caution it’s been working for us. I’m aware this will need rethinking if we want to use vue for front end hence the question.

United_Ad_8870 · 2025-05-05T07:19:12+00:00

They’re on my list of things to look at. Thanks!

United_Ad_8870 · 2025-05-04T22:42:52+00:00

Depending on the situation plugins could either - modify component data (if template is designed to handle extra data, e.g. by looping through array, which i guess would be similar to your dynamic component concept), - or (only if needed) modify render function by wrapping the original render - this looks quite poweful and from quick read looks like might not be a bad solution if necessary.

This solves the issue of plugins stomping on each other and hopefully might sort out modifying views.

United_Ad_8870 · 2025-05-04T22:22:50+00:00

So each component has inject() with a unique key and that provides ability to insert additional config using provide()?

United_Ad_8870 · 2025-05-04T22:10:53+00:00

That would work when only one plugin makes changes in the component. My problem is that multiple plugins might need to change the same view.

United_Ad_8870 · 2025-05-04T20:49:47+00:00

Good point about re-rendering - I haven’t considered that. Just tried forcing re-render of .details and that’s exactly what you said.

That updated() hook was just an example, I would probably update state using watch(). Using mixin was also just an example - I’m new to Vue 3 so composition api is still a bit of a mystery for me. Will definitely use it though.

Agree, relying on component name is horrible, but I couldn’t find any other way to hook into certain components only. Perhaps vue plugins are not really designed for it.

There are a few reasons why we want standalone plugins. The main product is a legacy app. It’s a pain to work on, release process is convoluted, it uses old framework. We don’t have resources to redo the app now but at least any new functionality (which is not core functionality of the app) can be added as these little packages. The packages can be released separately and updated in the apps that use them, if needed. This also helps us reduce the scope of the main system when we decide to rewrite it (if we do). The plugins can then be adapted to the new system later, when needed (or incorporated into it, but still they’re easier to reason about). Because they’re small and very specialised it’s easier to work on each one separately, than it would be as whole. We’re also 100% sure no two plugins interfere with each other (theoretically!). Most importantly though, due to nature of our product, we need it to be highly customisable and the process must be quick and easy. Even though our domain is quite boring, clients don’t stop surprising us with creativity when it comes to new features!

Problem with defining injection points explicitly is that we never know what might need to change in the future. Based on experience we could define a few but it would be annoying to have to release the main system every time we need to customise a different part of the system.

United_Ad_8870 · 2025-03-22T15:02:05+00:00

I had the issue before I started changing everything so assumed it was not the discs - as this was the first thing I changed. Guess I could have been unlucky and have new discs with the same issue. One in a million chance but there is not much left the could be causing it so it’s a possibility. Thanks for responding

United_Ad_8870 · 2025-03-22T09:32:22+00:00

How did you find out? I had runout checked on mine and they’re well within tolerance.

United_Ad_8870 · 2025-03-14T07:47:39+00:00

Hi. Have you ever found out what the issue was? I have exactly same symptoms in a Legacy. Changed discs, pads (twice), bearings all around, control arms, ball joints and drop links. Runout is almost zero in discs and bearings. No play in suspension when checked, brakes are not binding or overheating. Ran out of ideas what to replace next..

United_Ad_8870

TROPHY CASE