Prompt the user before adding source files to org

[Scott Wells]

Right now we automatically add source files to the org that are opened in editor windows (including those that have just been created). We should prompt the user before adding files.

[Vivek M. Chawla]

Agree. Adding (deploying, really) anything to an org should be a conscious choice, not something "accidental". A lot of the problems with Deployment and Retrieval in IC seem (to me) to be related to this kind of thing.

[Scott Wells]

For what it's worth, the reason I haven't addressed this one yet is that the Tooling API does not currently support compilation of metadata that hasn't yet been added to the org. As a result, if I were to prompt the user whether send locally-added files to the org and the user were to say no, I wouldn't be able to provide any validation feedback to the user until those files were in fact added. I'd have to make that very clear to the user to avoid confusion about the difference in behavior vs. files that do exist in the org.

[Vivek M. Chawla]

I see what you're saying. I can see how this would be tricky.

Maybe it's possible to have a small message somehow (or a small bug at the top of the code file) that indicates that certain features won't be available until the first save / deploy to the org.

Something like the little ! bug that shows at the top right of a code file when there are errors (see screenshot below)

[Scott Wells]

Yeah, I was thinking about showing it as an inspection that could be configured by the user as to whether it's shown as a warning or error or even not at all...same basic idea, though.