Skip to content
This repository has been archived by the owner on May 1, 2024. It is now read-only.

More user control over plugin execution #8

Open
joshuarli opened this issue Feb 24, 2018 · 2 comments
Open

More user control over plugin execution #8

joshuarli opened this issue Feb 24, 2018 · 2 comments
Assignees

Comments

@joshuarli
Copy link
Collaborator

joshuarli commented Feb 24, 2018

"Once installed, this plugin will automatically execute editorconfig.getApplyProperties on files when they are opened or saved."

So this is a pretty sane default IMO, but some users may want to configure it so that execution is disabled on file open and file save, so that a custom keybinding can be configured for plugin execution.

How should we go about implementing this @10sr? settings.json?

@10sr
Copy link
Owner

10sr commented Feb 25, 2018

I do not have any strong opinion for this.
I thinks there can be several ways to achieve this, for example following two options: IMO either way is OK !

  • Add two config boolean options: somethinkg like editorconfigdisableonsave and editorconfigdisableonopen
  • Add a option like editorconfigapplywhen, whose value should be an array and defaults to ["onSave", "onSave"]

@10sr 10sr closed this as completed Feb 25, 2018
@10sr 10sr reopened this Feb 25, 2018
@joshuarli
Copy link
Collaborator Author

I like the two disable boolean options, because they reflect that there are sane defaults yet the end user can choose to disable them in favor of a keybinding. I'll get around to implementing this when I have some time.

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

No branches or pull requests

2 participants