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

Pass the dir config options to plugins #1320

Merged
merged 2 commits into from
Jul 28, 2021

Conversation

MadeByMike
Copy link
Contributor

@MadeByMike MadeByMike commented Jul 19, 2020

I've found numerous cases where knowing the input and output dir is required for plugins.

Because of the execution of merging options it was not as simple as first imagined. I passed the responsibility for running plugins to the TemplateConfig class. This felt similar to a lot of other config options which are set and run later.

I'm looking for feedback on whether the raw config values should be passed as I've done here... or if we should resolve these further first? Also... should we pass anything else from TemplateConfig to plugins?

@MadeByMike MadeByMike changed the title [WIP] Pass the dir config options to plugins Pass the dir config options to plugins Aug 5, 2020
@zachleat zachleat merged commit 19e88f0 into 11ty:master Jul 28, 2021
@zachleat
Copy link
Member

Thank you! Only a year later 👀

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

Successfully merging this pull request may close these issues.

None yet

2 participants