Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep metadata about extension installation (install date, install source, etc.) #149812

Closed
Bobronium opened this issue May 18, 2022 · 1 comment
Closed
Assignees
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Milestone

Comments

@Bobronium
Copy link

Bobronium commented May 18, 2022

Metadata should contain at least:

{
    "installDate": 123456543,
    "updateDate": 123456543,
    "versionBeforeUpdate": "0.1.2",
    "dependencyOf": [], // list of installed extensions that require this one
    "partOfExtensionPacks": [], // list of installed extension packs containing this one
    "installedManually": true  // whether extension is installed by user or as an requirement or part of extension pack
}

It will allow to implement this features and fix weird behaviours:

This should be default and predictable behaviour of VSCode, since only then extension makers can rely on it.
This is why I don't think the argument in #53405 (comment) is applicable

Here's some pseudocode to show how logic could look like:

When extension installed by user

def write_metadata(extension):
    metadata = extension.metadata = {}
    metedata.installDate = now
    metadata.updateDate = now
    metadata.versionBeforeUpdate = null
    metadata.dependencyOf = set()
    metadata.partOfExtensionPacks = set()
    metedata.installedManually = true
    
    for dependency in extension.dependencies:
        dependency.dependencyOf.add(extension.name)
    
    for dependency in extension.pack:
        dependency.partOfExtensionPacks.add(extension.name)
@sandy081 sandy081 added feature-request Request for new features or functionality extensions Issues concerning extensions labels May 18, 2022
@sandy081 sandy081 added this to the Backlog milestone May 18, 2022
@isidorn isidorn added the *out-of-scope Posted issue is not in scope of VS Code label Dec 6, 2022
@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Dec 6, 2022
@vscodenpa
Copy link

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.

If you wonder what we are up to, please see our roadmap and issue reporting guidelines.

Thanks for your understanding, and happy coding!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
extensions Issues concerning extensions feature-request Request for new features or functionality *out-of-scope Posted issue is not in scope of VS Code
Projects
None yet
Development

No branches or pull requests

4 participants