Feature ideas

[aileftech]

If you think something is missing from SnapAdmin, please leave a comment with a short explanation of what you would like to see.

If somebody already commented with something similar, you can leave a reaction so I can gauge the interest in every feature.

[jamesmbowler]

I'd like to see role based permissions using spring security.

[aileftech]

Hi! This is "partially" supported as explained in the docs. You have to adapt your security configuration manually to protect the routes the way you wish. Were you referring to some deeper integration or something different?

[jamesmbowler]

Oh, nice! Great project, thanks!

[kamlesh0606]

1. When Product Edit/Add Flow, apply custom validation Or Custom Logic Over Data Save.
2. Apply Role on Add, Edit, View, Delete, Export on Api
3. callback Function When Data Save For update to other place Like cache Or depended Flow
4. Data Encryption Like AES 256 , ...
5. Secure Field Manage Like Password , Email Id , SSN Number, User Profile Data for Manage HIPPA Policy
6. Image save in File Storage and Details update at DB Side Like Name , UUID Id of image.
7. Depended Master selection Like Product needs category , Tag , Company. May be Select 1 Or More.
8. Audit Logs For Data Edit , Update , Delete. if Data Secure then provide View also

[BlackHornet]

I really like the project, looks really great to provide a very nice GUI to manage my data.
One thing I am missing so far ist the support for embedded data.

For example I would like to define localizable properties in my entity using @embeddables and @ElementCollection.

Another thing would be the options to really use UUID fields like for example:
@id
@GeneratedValue
protected UUID uid;

Using this in my Entity is throwing an error in SnapAdmin, when I try to delete an entity, that it provides a String, not an UUID.

Could this being added in the future as well?

[BlackHornet]

Not sure how difficult this would be, but it would be awesome if you have a relationship (lets say Entity A has Relationships to Entity B), that in the Entity A you have the option to really add Entity B items directly without having to create B for itself, and then look up the reference in another step afterwards in A.
Could make it so much easier to manage related elements.
Something like this comes up in my mind:

Regards