Any suggestions how to surface this without annoying the user? (how would disallow differ from cancel?)

The problem here is that after a disallow the dialog doesn't show up anymore. So no way to trust the workspace later without using the dev tools and editing local storage

@dbaeumer yes, the workarounds being moving the folder or changing local storage. The alternative is using user setting to drive this instead of local storage. Seems a bit messy doing that since paths generally aren't portable across machines and it's workspace-specific config in your user settings.

Since the use case of a user re-enabling this at a later time seems to be so small I don't think it's worth changing this. The usage numbers for workspace shell's were really small when I looked at them so the chance that a user would choose to disallow and later make a conscious decision to allow seems really slim. Closing as designed for now, will listen for feedback.

Strange. I was forced to do this for PHP :-). I simply added a context sensitive command to clear local storage.

@dbaeumer maybe a command would be good, still not for this version. The multi-root discussion we're having at the moment may actually impact this.