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

Is there a way to disable by project ? #22

Closed
jpbelang opened this issue May 8, 2019 · 4 comments
Closed

Is there a way to disable by project ? #22

jpbelang opened this issue May 8, 2019 · 4 comments

Comments

@jpbelang
Copy link
Contributor

jpbelang commented May 8, 2019

I have a bunch of projects and would like to activate by project.

Is this a feature that would be feasible ?

(That said, this code is really cool :-) )

@dkandalov
Copy link
Owner

Yes, I thought about something like that a while ago (see issue #11).
What do you mean by "activate by project"? Have all settings configured per project?

@jpbelang
Copy link
Contributor Author

Pretty much (or maybe override by project). I have some projects no written by me that don't work well with TCR (where the tests can fail in surprising ways). Even the size of the commits can get out of hand because of changing data. In these projects, I'd like to either stop the plugin entirely or partly.

In my projects, I'm rather enjoying using it and it's really helping the flow of my work in general.

@dkandalov
Copy link
Owner

I had pretty much the same experience. The main reason I didn't implement it was that updating the same setting for each project can be very tedious. Maybe this is not really a problem and I should just try per-project settings.

dkandalov added a commit that referenced this issue Jun 26, 2019
@dkandalov
Copy link
Owner

I made all plugin settings to be scoped by current project.
Unfortunately, your current application-level settings will be lost on plugin update (because it's not very clear how to do migration, should the current settings become default for all new projects? probably not).

This should work starting from v0.3.6 once it's approved by jetbrains.

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

No branches or pull requests

2 participants