Siim Kallari
@humunuk.bsky.social
Developer/Ex-CTO/"IT-guy"
Organizing Digit (https://digit.dev), freelancer, father, love music, love dancing.
Over 8yrs of PHP, Laravel, JavaScript
Can handle Linux, servers
Advocate of self-development.
My weird-secret love is legacy systems (PHP)
Organizing Digit (https://digit.dev), freelancer, father, love music, love dancing.
Over 8yrs of PHP, Laravel, JavaScript
Can handle Linux, servers
Advocate of self-development.
My weird-secret love is legacy systems (PHP)
Been always proponent of writing tests, sometimes "tests first", but for this project I chose different test framework (PEST instead of PHPUnit) and I gotta say that, PEST is not my cup of tea. Too many abstractions, too many hidden things. Not OOP but also not FP, but now is late to switch back
December 4, 2024 at 12:53 PM
Been always proponent of writing tests, sometimes "tests first", but for this project I chose different test framework (PEST instead of PHPUnit) and I gotta say that, PEST is not my cup of tea. Too many abstractions, too many hidden things. Not OOP but also not FP, but now is late to switch back
Not only, using a Model Policy will give you even more options.
Say that user can add something, but not delete it. Simple :)
create() -> true
delete() -> false
and UI updates itself to show those buttons
Say that user can add something, but not delete it. Simple :)
create() -> true
delete() -> false
and UI updates itself to show those buttons
December 3, 2024 at 11:43 AM
Not only, using a Model Policy will give you even more options.
Say that user can add something, but not delete it. Simple :)
create() -> true
delete() -> false
and UI updates itself to show those buttons
Say that user can add something, but not delete it. Simple :)
create() -> true
delete() -> false
and UI updates itself to show those buttons
Have a good recovery!
December 2, 2024 at 9:14 AM
Have a good recovery!