Add zenstruck/foundry

[kbond]

Q	A
License	MIT
Doc issue/PR	symfony/symfony-docs#14731

Based on slack discussions with @weaverryan & @wouterj.

Foundry has the concept of auto-refreshing entities - prior to 1.9, this was disabled by default as there are caveats (entity changes silently lost). In 1.9, the caveats still exist but we were able to throw a helpful exception. We would now like auto-refreshing entities enabled by default but this would be a BC break in 1.x. A recipe to enable in 1.x was decided as the next best thing.

The double config is unfortunate but we couldn't think of a better way.

Likely we'll want a post-install.txt and probably some config comments?

[ghost]

Pull request passes validation.

[Nyholm]

Thank you @kbond, Is this still "WIP"?

I would be happy to merge this recipe.

[ghost]

Pull request passes validation.

[kbond]

I removed the WIP/RFC. I believe this will work as expected as is. Just a few outstanding questions:

1. Should I add a post-install.txt?
2. Should the double config be handled differently or comments added for an explaination?
3. Any other comments in the config?

[ghost]

Pull request passes validation.

[kbond]

FYI, zenstruck/foundry 1.9 is now released.

[Nyholm]

Should I add a post-install.txt?

If there is a reason to add one, then yes. Im not sure what that reason is. What would you like to tell the user?

Should the double config be handled differently or comments added for an explaination?

Will the config always be the same? If so, we can keep it. We are currently only using one config options, so we can also keep it simple.
It does not matter too much for me. I would do what @OskarStark suggestes.

Any other comments in the config?

You could add a link to your bundles docs.

[ghost]

Pull request passes validation.

[kbond]

I added some config comments and a post-install.txt for review.

[ghost]

Pull request passes validation.

[Nyholm]

Thank you