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
// A __GDPR__FRAGMENT__ has no meaning until it is ${include}d by a __GDPR__ comment, at which point
3203
+
// the included properties are effectively inlined into the __GDPR__ declaration. In this case, for
3204
+
// example, any __GDPR__ comment including the TypeScriptCommonProperties will be updated with an
3205
+
// additional version property with the classification below. Obviously, the purpose of such a construct
3206
+
// is to reduce duplication and keep multiple use sites consistent (e.g. by making sure that all reflect
3207
+
// any newly added TypeScriptCommonProperties). Unfortunately, the system has limits - in particular,
3208
+
// these reusable __GDPR__FRAGMENT__s are not accessible across repo boundaries. Therefore, even though
3209
+
// the code for adding the common properties (i.e. version), along with the corresponding __GDPR__FRAGMENT__,
3210
+
// lives in the VS Code repo (see https://github.com/microsoft/vscode/blob/main/extensions/typescript-language-features/src/utils/telemetry.ts)
3211
+
// we have to duplicate it here. It would be nice to keep them in sync, but the only likely failure mode
3212
+
// is adding a property to the VS Code repro but not here and the only consequence would be having that
3213
+
// property suppressed on the events (i.e. __GDPT__ comments) in this repo that reference the out-of-date
0 commit comments