You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Instead of depending directly on flysystem a filesystem abstraction could be made (with adapters for flysystem, gaufrette and others).
Besides allowing different filesystem abstractions it will also allow us to have other methods in the filesystem interface, i.e.: function isDeeplinkingAvailable(): bool and function getDeeplink(): string. The latter method would generate a direct link to the feed instead of having to go through the ShowFeedAction.
The text was updated successfully, but these errors were encountered:
isn't flysystem an abstraction already for filesystems?
Yes :D
However, making an abstraction doesn't mean you have to use another abstraction to utilize it. You can also create your own concrete implementation. Anyway, do you have an idea to the problem with deeplinking that could solve it without introducing another filesystem abstraction?
Hi! I know it's an old subject, but I'd like to know if there's any update about it.
Knowing the fact Sylius uses KnpGaufrette, it forces us to use 2 different filesystem configurations. With complex ecosystems (cloud storage for assets/static files, multi-pod environment...) it's starting to become a bit painful to have it all working (or we have to override the services using flysystem).
Instead of depending directly on flysystem a filesystem abstraction could be made (with adapters for flysystem, gaufrette and others).
Besides allowing different filesystem abstractions it will also allow us to have other methods in the filesystem interface, i.e.:
function isDeeplinkingAvailable(): bool
andfunction getDeeplink(): string
. The latter method would generate a direct link to the feed instead of having to go through theShowFeedAction
.The text was updated successfully, but these errors were encountered: