Back
HungryBus

HungryBus

@HungryBus

I'm already in my 2nd Filament app where I write the logic for custom dynamic fields (had multiple apps with native Laravel with this kinda logic as well).

The idea is pretty simple: the user can create fields (text, textarea, number, email, select, etc.) and designate them to any resource they like and then use these in the form as if these were hard-coded in the form() method.

Fields are stored in DB, field data is stored in a separate table and has a morphMany relation.

Should I create a package for it? It'd be my very first one, so not sure if this is gonna be needed at all...

image

image

2 • •

195

•
HungryBus

HungryBus

@HungryBus

In response to @benzo

I was thinking about this one, but this is more for a form itself, that's not really related to a resource. In my current use case, I want just to add fields to a resource's form that are saved via relation and displayed at a resource itself. Bolt is great when you want to add dynamic forms from scratch without binding responses to any resource (only to Responses model of the Bolt itself)

1 • •

214

•
  • No matching results...
  • Searching...

/ 1000

benzo

benzo

@benzo

Ok this can be interesting, if it suits your needs and decide to make a package, please provide application examples 👍

• •

115

•