You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Insiders notification immediately after install #7586
Our team has been trying to minimize the amount of notifications that show, particularly after install or startup. This one seems particularly bad as I installed the CPP extension for the first time (or first time in a long time), and was asked if I wanted to use the insiders version:
Please rethink when it's presented also to non-codespaces. For example, a slightly less intrusive option would be when you open a cpp file for the first time, as opposed to on start up.
Additional idea: only offer this for advanced users after some usage period. You can detect advanced users for example if they started debugging or used some refactoring...
I do not think it is a good idea to show this to a novice user as soon as he installs. Why would a novice user use insiders.
The prompt won't appear unless a C/C++ "real activation" event occurs. You may have had a c_cpp_properties.json file in your workspace folder, or you may have opened a C/C++ file, etc.
Showing the prompt after a certain number of real activations seems fine to me -- how many activations should we require?
Activity
isidorn commentedon May 25, 2021
Yes, agree 100% here.
Another issue is that this is on startup, which we always recommend against.
bobbrow commentedon May 25, 2021
We currently disable it for Codespaces as that was the case we have prioritized reducing notifications for.
Tyriar commentedon May 25, 2021
Please rethink when it's presented also to non-codespaces. For example, a slightly less intrusive option would be when you open a cpp file for the first time, as opposed to on start up.
isidorn commentedon May 25, 2021
Additional idea: only offer this for advanced users after some usage period. You can detect advanced users for example if they started debugging or used some refactoring...
I do not think it is a good idea to show this to a novice user as soon as he installs. Why would a novice user use insiders.
bobbrow commentedon May 25, 2021
Fair enough. We can come up with a criteria that should be met before prompting.
sean-mcmanus commentedon May 25, 2021
The prompt won't appear unless a C/C++ "real activation" event occurs. You may have had a c_cpp_properties.json file in your workspace folder, or you may have opened a C/C++ file, etc.
Showing the prompt after a certain number of real activations seems fine to me -- how many activations should we require?