Skip to content

Conversation

tacman
Copy link

@tacman tacman commented Jan 3, 2024

Helps with #101

@kbond
Copy link
Member

kbond commented Jan 3, 2024

This package can be used fully independent from Symfony so I don't want to change the type in the root composer.json.

My long-term plan for this package is to split out the Symfony integration (keeping this the monorepo but a subtree split for zenstruck/filesystem-bundle). At that point, this package would be type: symfony-bundle.

As for when this will happen, I'm not sure. I use this package in my projects with great success but I'm waiting to see if there is community adoption before releasing 1.0 and splitting the packages (as it's a lot of work).

@tacman
Copy link
Author

tacman commented Jan 3, 2024 via email

@kbond
Copy link
Member

kbond commented Jan 3, 2024

Yep, the flysystem bundle just wraps flysystem.

This package wraps flysystem but with an alternate object-oriented api (files/directories are objects you can pass around).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants