Backpex.Fields.InlineCRUD - adding handling embeds_one to

[thanos]

I've need of this at the bank I work at and it makes sense to eventually cover all of ecto's fields types.
I have tried to do the changes as unobtrusive as possible and I'm not doing the pull request
as I can't think of a good example to code for your Example site.

1. I thought I could add an embeds_one field to invoices {net, tax, total}, and then add a Reasource Action to invoice users? But it doesn't really test edit, as invoices are an example of immutable.
2. Another idea is to add an upload schema simulating an S3 backend. The field could hold {bucket, key, eTab, timestamp}. This is one of the real use cases at my work. But I would need to add a schema, migration etc.

Any ideas would be great, and of course: Many thanks for the great work!

[Flo0807]

Hey!

If you have something ready to submit as a pull request, go for it! Which fields are working in your solution already?

We can find a use case for the demo later. Perhaps something for the products, such as product attributes or variants? Ideally, it should be easy to understand.

[thanos]

Thanks @Flo0807 will do this weekend. Much better than mowing the lawn!