Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Change config to support different configurations per file pattern #115

Merged
merged 1 commit into from
Jan 23, 2021

Conversation

simonihmig
Copy link
Owner

@simonihmig simonihmig commented Jan 23, 2021

This changes the configuration options considerably. Instead of having one or multiple configurations based on a dedicated folder (where no other files than those to be processed according to that configuration must be present), this is not based on include (and exclude) globs.

This way you are flexible in your file layout, you can have all images in one folder for example, and still provide different configurations for every file (or subset of files).

Besides the configuraton change, another breaking change is now the requirement to provide the full file path to the <ResponsiveImage> component, like <ResponsiveImage @image="assets/images/landscape.jpg">. But this removes the ambiguity when having multiple images with the same name but in different folders, and also is more aligned to a plan HTML image tag (<img src="assets/images/landscape.jpg">).

Closes #50 and #54.

/cc @andreasschacht @lolmaus

@simonihmig simonihmig merged commit f311f85 into dev-v2 Jan 23, 2021
@simonihmig simonihmig deleted the config branch January 23, 2021 16:59
This was referenced Jan 23, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant