Loading video...

Video Failed to Load

Go Home

Use the “resource:permission” naming convention for better code hinting. From our Permission Systems that Scale course with @‌DevSimplified.

20,927 views • 7 months ago •via X (Twitter)

9 Comments

Travis Watson's profile picture
Travis Watson7 months ago

resource first, or permission first... why not both? 🙃

Sujithkumar's profile picture
Sujithkumar7 months ago

@hameedraha @Hadi_raha 😅 we were always ahead!!

Pramod Sharma 🏗️ Frontend Architect's profile picture
Pramod Sharma 🏗️ Frontend Architect7 months ago

This pattern ages really well in larger codebases. Reads clean now, saves you from permission chaos later.

Grimz's profile picture
Grimz7 months ago

Good point and I totally agree.

con Cero's profile picture
con Cero7 months ago

Abstraction is a game changer

ikraam's profile picture
ikraam7 months ago

This is a really good tip

Ogla Sungutay🔺's profile picture
Ogla Sungutay🔺7 months ago

Agreed.

Aleksa Mitić's profile picture
Aleksa Mitić7 months ago

Definitely implementing this with my next RBA

Aaron McAdam's profile picture
Aaron McAdam7 months ago

But why “resource:permission” over “resource_permission”?

Related Videos