Skip to content

Insiders notification immediately after install #7586

Closed

Description

@Tyriar

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:

Screen Shot 2021-05-25 at 5 02 33 AM

cc Isidor Nikolic (@isidorn) Devin Valenciano (@devinvalenciano)

Activity

  1. isidorn commented on May 25, 2021

    @isidorn

    Yes, agree 100% here.
    Another issue is that this is on startup, which we always recommend against.

  2. bobbrow commented on May 25, 2021

    @bobbrow
    Contributor

    We currently disable it for Codespaces as that was the case we have prioritized reducing notifications for.

  3. Tyriar commented on May 25, 2021

    @Tyriar
    Author

    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.

  4. isidorn commented on May 25, 2021

    @isidorn

    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.

  5. bobbrow commented on May 25, 2021

    @bobbrow
    Contributor

    Fair enough. We can come up with a criteria that should be met before prompting.

  6. sean-mcmanus commented on May 25, 2021

    @sean-mcmanus
    Contributor

    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?

  7. added
    fixedCheck the Milestone for the release in which the fix is or will be available.
    on May 25, 2021
  8. locked and limited conversation to collaborators on Jul 10, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

Language ServiceenhancementImprovement to an existing featurefixedCheck the Milestone for the release in which the fix is or will be available.quick fix

Type

No type

Projects

No projects

    Milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions