Skip to content
This repository has been archived by the owner on Nov 10, 2022. It is now read-only.

Plugin model for cleanup passes #11

Open
MeTaNoV opened this issue Dec 2, 2015 · 5 comments
Open

Plugin model for cleanup passes #11

MeTaNoV opened this issue Dec 2, 2015 · 5 comments

Comments

@MeTaNoV
Copy link

MeTaNoV commented Dec 2, 2015

I did not find any place where all available mixin are aggregated.
Maybe Tedium is a good candidate to build such dictionary across the component database?

@rictic
Copy link
Contributor

rictic commented Dec 5, 2015

As a first step, a more structured representation of the cleanup passes, and the ability to control them a la #1.

If we get enough cleanup passes a plugin model could prove useful.

@rictic rictic changed the title Mixin dictionnary task Plugin model for cleanup passes Dec 5, 2015
@MeTaNoV
Copy link
Author

MeTaNoV commented Dec 6, 2015

seems a good first step indeed!
I did not try it yet, but is Tedium already useable on a component basis? (or just the Google set hard-coded?)

@rictic
Copy link
Contributor

rictic commented Dec 9, 2015

Currently it's hardcoded to the PolymerElements org unless you specify the repos using the --repo CLI arg. With configurable passes & repos then it's much more likely to be useful for others.

@MeTaNoV
Copy link
Author

MeTaNoV commented Dec 9, 2015

That's perfect indeed! Thanks Peter ( @rictic ) PS: saw it a minutes after I posted the comment in other PRs :)

@rictic
Copy link
Contributor

rictic commented Jan 12, 2016

We've made some progress on this, but currently all passes need to be checked into tedium itself. How should tedium discover other passes that you'd like to run?

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

No branches or pull requests

2 participants