Closed IsraelOrtuno closed 2 years ago
What about using spatie/laravel-schemaless-attributes for implementing this?
It's funny that an attributes package will be using another attributes package 😅
Anyway if this proposal is gonna be considered, we should drop the current is_required
field.
I do actually like the package, but isn't a bit tricky to make users learn how to user other package for a simple JSON column?
I agree, let's do it the simple way 👍
Have you considered adding validation rules to attributes?
More details please.. 🤔
It was just a quick thought, not sure if makes sense at all but something like being able to set an array of Laravel validation rules to Value models.
Well, I'd love to see something like that 😋
@IsraelOrtuno Any update?
Closing this issue due to inactivity. However, the idea is still valid and I'd be happy to consider any PRs! 😉
I was thinking about adding a
options
JSON like column into the attributes table (or maybe intoattribute_entity
?) so it could store some extra information about the attribute that can be used to customise the attribute behaviour in the application.From the package point of view, it would just be a write/read column, so no extra coding needed.
We can se an example of a practical usage (field options):
Thoughts?