Skip to content

Update GDPR annotations #27242

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

Merged
merged 2 commits into from
Sep 21, 2018
Merged

Update GDPR annotations #27242

merged 2 commits into from
Sep 21, 2018

Conversation

sandersn
Copy link
Member

  1. Use TypeScriptCommonProperties -- after moving Typescript to the extension extract step in https://github.com/Microsoft/vscode-gdpr-tooling/pull/4, TypeScriptCommonProperties is properly resolved.
  2. Add projectInfo. Based on what @kieferrm said, I think that EndUserPseudonymizedInformation is correct for projectInfo.

@sandersn sandersn requested a review from amcasey September 20, 2018 21:31
@@ -46,6 +46,8 @@ namespace ts.server {

/* __GDPR__
"projectInfo" : {
"${include}": ["${TypeScriptCommonProperties}"],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Did we figure out how this interacts with version below?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The included one overrides the local one. I think I'll leave it in since TypeScriptCommonProperties could (in theory) also remove properties over time as well as add more.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird that the local one wouldn't win, but I agree that keeping both makes sense.

@@ -46,6 +46,8 @@ namespace ts.server {

/* __GDPR__
"projectInfo" : {
"${include}": ["${TypeScriptCommonProperties}"],
"projectInfo": { classification: "EndUserPseudonymizedInformation", purpose: "FeatureInsight" },
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe an endpoint is mandatory for EUPI (i.e. you're probably missing a property).

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

That's not what the documentation says -- it says that 'none' is right for almost everything except a few common properties.

1. Add quotes where missing.
2. Fix name, which was projectInfo by mistake.
3. Add an endpoint of "ProjectId".
@sandersn
Copy link
Member Author

Well, the endpoint "ProjectId" doesn't make the gdpr tool fall over, so I'll check with @kieferrm about using it.

@sandersn
Copy link
Member Author

Actually, ProjectId refers to VS project ids not VS Code ids, I believe, so I'm not sure it makes sense here.

Copy link
Member

@amcasey amcasey left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think "ProjectId" is the right endpoint. Thanks!

@@ -46,6 +46,8 @@ namespace ts.server {

/* __GDPR__
"projectInfo" : {
"${include}": ["${TypeScriptCommonProperties}"],
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Weird that the local one wouldn't win, but I agree that keeping both makes sense.

@sandersn sandersn merged commit 336be23 into master Sep 21, 2018
@sandersn sandersn deleted the update-gdpr-annotations branch September 21, 2018 17:55
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants