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
So currently there are a bunch of default plugins, such as Git, ProjectFile, etc. If you want to not use one of those plugins in your template, you do Template(; disable_defaults=[Git], plugins=[...]), which I've always thought was kind of clunky.
So... what if we overload ! for Type{<:Plugin} to allow for Template(; plugins=[PluginIWant, !DefaultIDontWant])?
I think it really has the same short-term discoverability as disable_defaults because you're going to have to look at the docstring for either one, and ! is IMO easier for users in the long term as they only have to worry about one keyword (plugins).
Maybe this is a terrible idea, so please don't hesitate to tell me so (or to tell me that you love the idea).
The text was updated successfully, but these errors were encountered:
So currently there are a bunch of default plugins, such as
Git
,ProjectFile
, etc. If you want to not use one of those plugins in your template, you doTemplate(; disable_defaults=[Git], plugins=[...])
, which I've always thought was kind of clunky.So... what if we overload
!
forType{<:Plugin}
to allow forTemplate(; plugins=[PluginIWant, !DefaultIDontWant])
?I think it really has the same short-term discoverability as
disable_defaults
because you're going to have to look at the docstring for either one, and!
is IMO easier for users in the long term as they only have to worry about one keyword (plugins
).Maybe this is a terrible idea, so please don't hesitate to tell me so (or to tell me that you love the idea).
The text was updated successfully, but these errors were encountered: