Ignore Upload some settings information in GIST

[borekb]

Originally from #100 (comment)

Since #100, local settings can be replaced by replaceCodeSettings. However, this doesn't influence upload direction at all and if something changes frequently, there will be lots of new versions in the Gist for no good reason.

It would be good if replaceCodeSettings could also be taken into account during upload and replace the real value with some placeholder or something.

[rainbyte]

I think this would be useful, e.g.:

• desktop vscode usually has "window.zoomLevel": 2
• on my notebook I prefer "window.zoomLevel": 0

It would be better to just ignore that setting.

[shanalikhan]

@rainbyte
For now, On desktop you need to set
"replaceCodeSettings": {
{ "name :"window.zoomLevel",
"value":2
}
}
and for notebook , same way

[rainbyte]

Thanks @shanalikhan, that's what I'm doing now, it just doesn't feel right.

I would prefer to ignore the setting globally, without config per machine, if it is possible.

[fredrikaverpil]

@borekb @shanalikhan if I read this right, you want any replacement code to be removed from the settings.json in the gist.

This would be nice, I agree, but please do not remove comments in settings.json which may contain these strings. I keep all of my different machine setups in the main settings.json file as comments.

[borekb]

I wouldn't remove the value from the uploaded JSON, I would just replace it with some known, single value.

For example, say that some settings stores a timestamp. Currently, if I upload the settings every second, I'll get many revisions of my settings.json with mess like this:

Gist v1:
option.timestamp: 1488289783

Gist v2:
option.timestamp: 1488289784

Gist v3:
option.timestamp: 1488289785

The goal would be to replace the ever-changing value with a single, non changing value, e.g., 1488289783 (it doesn't really matter). Now, when I invoke Upload settings every second, I won't get new versions of settings.json in my Gist.

[shanalikhan]

@borekb which setting key is changing, can you explain the real example of any extension of anything that cause change in values in settings.json again and again

[borekb]

@shanalikhan for me, it's window.zoomLevel. I change it frequently.