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
The original use case was to generically create image styles that can be reused rather than specifically having to define image styles in the consuming code, but I understand your point about portability of the components and possibly the flexibility of being able to specify an image style on-the-fly.
Although this shouldn't be too difficult to implement, it does create more of a surface area for testing. Also, the way processed imaged are stored is in a directory which has the same name as the image style key. I think it would be necessary to not only define the image style on the component itself, but also to specify a key that should be used for storing the images in a maintainable way.
I don't have an time to prioritise this right away due to other commitments, but let's keep this open for now. If I get some time then I can pick this up myself. Otherwise contributions are welcome, subject to there being good test coverage.
Ideally, components should be able to declare their own style with no need for it to exist in
nuxt.config.js
. For example:This would make components much more reusable across projects.
The text was updated successfully, but these errors were encountered: