search

vjekob / al-objid

Manage object IDs in multi-user environments with mind-boggling simplicity.
MIT License
29 stars 17 forks source link

Remember setting to not synchronize a certain workspace #10

Closed ajkauffmann closed 3 years ago

ajkauffmann commented 3 years ago

In an individual workspace, you will get a popup 'Do you want to synchronize' every time when using ctrl+space to get an object id. It doesn't remember when I click No.

Could it remember that I don't want to use Object ID Ninja in a particular workspace?

waldo1001 commented 3 years ago

Just Sync¨🤪

ajkauffmann commented 3 years ago

Why would I do that?

waldo1001 commented 3 years ago

Why not?

ajkauffmann commented 3 years ago

I'm used to creating many small apps, just to test or figure out stuff. There is simply no need to sync object id's for those apps.

waldo1001 commented 3 years ago

Ah .. yeah .. that makes sense 😉 (I was actually just teasing you ;-))

vjekob commented 3 years ago

From my perspective, it's pointless to have Ninja remember that you don't want to use it in a workspace. That's what VS Code already does, and it's called "Disable (Workspace)" and you can choose which extensions are enabled or disabled per workspace. So - if you don't want Ninja to monitor an app, just disable it for that app.

Furthermore, you can maybe already see in the code that Ninja will only ask you once to synchronize. Then it will remember your choice of "No" and won't bug you for the duration of that VS Code session. This is not yet released, because I have some minor things I want to do around it, but it's coming.

However, I don't think why you would both want to have Ninja enabled for an extension and have it not do its job. Either you enable it, sync, and use it, or you disable it and live happily ever after. But you do have this choice already.

Do you agree?

ajkauffmann commented 3 years ago

I see your point, didn't think about disabling / enabling it. Makes sense! But I would rather do it the other way around. Disable it globally and enable it per app. That's less work 😉

vjekob commented 3 years ago

Either way, it's something VS Code already allows you to control.

I'll do some final touches to asking this nagging question, and then let it stay as is.

vjekob commented 3 years ago

There, I've just published version 1.2.1 - it fixes this.

I am closing this issue, if you think we need to talk more about it, let me know and I'll reopen.