Skip to content

Commit bffe7a7

Browse files
committed
2.7.3
- Upgraded dependencies - Added a CHANGELOG.md - Added a CONTRIBUTING.md
1 parent bce90f9 commit bffe7a7

File tree

13 files changed

+1351
-704
lines changed

13 files changed

+1351
-704
lines changed

.gitignore

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -2,3 +2,4 @@ out
22
node_modules
33
*.vsix
44
typings
5+
.vscode-test

.vscode/launch.json

Lines changed: 11 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -1,6 +1,6 @@
11
// A launch configuration that compiles the extension and then opens it inside a new window
22
{
3-
"version": "0.1.0",
3+
"version": "0.2.0",
44
"configurations": [
55
{
66
"name": "Launch Extension",
@@ -10,19 +10,23 @@
1010
"args": ["--extensionDevelopmentPath=${workspaceRoot}" ],
1111
"stopOnEntry": false,
1212
"sourceMaps": true,
13-
"outDir": "${workspaceRoot}/out/src",
13+
"outFiles": [
14+
"${workspaceFolder}/out/src/**/*.js"
15+
],
1416
"preLaunchTask": "npm"
1517
},
1618
{
1719
"name": "Launch Tests",
1820
"type": "extensionHost",
1921
"request": "launch",
2022
"runtimeExecutable": "${execPath}",
21-
"args": ["--extensionDevelopmentPath=${workspaceRoot}", "--extensionTestsPath=${workspaceRoot}/out/test" ],
22-
"stopOnEntry": false,
23-
"sourceMaps": true,
24-
"outDir": "${workspaceRoot}/out/test",
25-
"preLaunchTask": "npm"
23+
"args": [
24+
"--extensionDevelopmentPath=${workspaceRoot}",
25+
"--extensionTestsPath=${workspaceRoot}/out/test/suite/index"
26+
],
27+
"outFiles": [
28+
"${workspaceFolder}/out/test/**/*.js"
29+
]
2630
}
2731
]
2832
}

CHANGELOG.md

Lines changed: 111 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,111 @@
1+
# Change Log
2+
All notable changes to the "code-sync" extension will be documented in this file.
3+
4+
The format is based on [Keep a Changelog](http://keepachangelog.com/en/1.0.0/)
5+
and this project adheres to [Semantic Versioning](http://semver.org/spec/v2.0.0.html).
6+
7+
## [Unreleased]
8+
9+
## [2.7.3] - 2020-10-10
10+
## Added
11+
- Added a CHANGELOG.md
12+
- Added a CONTRIBUTING.md
13+
14+
## Removed
15+
- Removed support for VSCode 1.13 making the minimum required VSCode version 1.14 because the minimum `@types/vscode` version is 1.14. This is a minor version bump because VSCode 1.13 is over 3 years old now so nobody should be using that version.
16+
17+
## Fixed
18+
- Upgraded dependencies
19+
20+
## [2.7.2] - 2020-05-17
21+
## Fixed
22+
- Fix Linux VSCode non Snap package bug
23+
24+
## [2.7.1] - 2020-05-09
25+
## Fixed
26+
- Bug where extension would not load in some cases due to not being able to find `settings.json`
27+
- Bug where extensions would not export correctly
28+
29+
## [2.7.0] - 2020-05-09
30+
## Added
31+
- If you use a non standard install of VSCode you can now set the name of the VSCode executable or the VSCode user settings path that CodeSync will use. The new commands added are `CodeSync: Set VSCode executable name` and `CodeSync: Set VSCode settings path`. See #41. Thanks to @convexshiba for this feature request.
32+
33+
## [2.6.2] - 2020-01-03
34+
## Fixed
35+
- Code not found on path errors when VSCode was installed through Snap on Linux. See https://github.com/golf1052/code-sync/issues/38
36+
37+
## [2.6.1] - 2019-10-13
38+
## Fixed
39+
- CodeSync will not migrate your settings files from a previous version of CodeSync if your current CodeSync version already has settings files. This means that any new settings will not be overwritten by your previous version's settings.
40+
- The status bar will now be correctly reset if CodeSync could not find VSCode's settings file when trying to export settings.
41+
- Added more logging when exporting settings.
42+
43+
## [2.6.0] - 2019-10-12
44+
## Fixed
45+
- Updated chokidar to version 3 which should [provide performance improvements](https://paulmillr.com/posts/chokidar-3-save-32tb-of-traffic/).
46+
47+
## [2.5.3] - 2018-01-03
48+
## Fixed
49+
- Export extensions after import has completed. Rarely, CodeSync would not be able to export extensions before the extension was deactivated so this guarantees the list of installed extensions gets saved at least once.
50+
51+
## [2.5.2] - 2018-01-02
52+
## Fixed
53+
- Only tries to install extensions that are not reported as being installed when importing extensions. Fixes https://github.com/golf1052/code-sync/issues/30. Thanks to @wesmdemos for the report.
54+
55+
## [2.5.0] - 2017-10-08
56+
## Added
57+
- Adds support for the Insiders version of VSCode. See https://github.com/golf1052/code-sync/issues/26. Thanks to @brianary for the report.
58+
59+
## [2.4.0] - 2017-08-10
60+
## Added
61+
- Adds the ability to toggle the status bar icon. See https://github.com/golf1052/code-sync/issues/25. Thanks to @gnowland for suggesting this.
62+
- Also added logging. CodeSync will log what it is doing in an output channel called CodeSync. If you have issues please include your CodeSync log.
63+
64+
## [2.3.2] - 2017-07-26
65+
## Fixed
66+
- Actually fix https://github.com/golf1052/code-sync/issues/23
67+
68+
## [2.3.1] - 2017-07-23
69+
## Fixed
70+
- Fixed https://github.com/golf1052/code-sync/issues/23
71+
72+
## [2.3.0] - 2017-07-22
73+
## Added
74+
- Added support for local settings. Thanks to @drdaeman for the idea: https://github.com/golf1052/code-sync/issues/17
75+
76+
## Fixed
77+
- Mitigated https://github.com/golf1052/code-sync/issues/9. You will now be able to use CodeSync to import or export settings, snippets, or keybindings even if CodeSync thinks `code` is not on your path.
78+
- Provided workaround for https://github.com/golf1052/code-sync/issues/19. See the README on how to uninstall extensions with CodeSync installed.
79+
80+
## [2.2.0] - 2017-02-08
81+
## Changed
82+
- Instead of exporting on extension deactivate, export when files change by using file watcher. This improves the reliability of auto file exporting.
83+
84+
## [2.1.2] - 2017-02-07
85+
## Fixed
86+
- More checks for empty files
87+
88+
## [2.1.1] - 2016-12-03
89+
## Fixed
90+
- When changing external sync path, reset extensions path (see https://github.com/golf1052/code-sync/pull/15)
91+
92+
## [2.1.0] - 2016-09-15
93+
## Added
94+
- New command to re-setup the external sync location
95+
96+
## Fixed
97+
- Don't wipe out settings if settings file is blank
98+
99+
## [2.0.0] - 2016-08-07
100+
- Rewrote extension
101+
102+
## [1.0.2] - 2016-01-01
103+
## Fixed
104+
- CodeSync will now migrate settings to the new version folder when upgrading.
105+
106+
## [1.0.1] - 2015-12-31
107+
## Fixed
108+
- Needed to add version number for code-sync extension folder
109+
110+
## [1.0.0] - 2015-12-31
111+
- Initial release

CONTRIBUTING.md

Lines changed: 17 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,17 @@
1+
# Contributing
2+
3+
## Testing and Building
4+
5+
I typically test this extension with the Node LTS version. As of 2020-10-10 that is 12.19.0.
6+
7+
When prepping a new version don't change the version number in [`package.json`](./package.json) AND [`src/cs.ts`](./src/cs.ts) until you're done with all your changes. If you want to modify/test settings migration upon a new version change the version number while working on changes.
8+
9+
## Pushing Changes
10+
11+
Make sure you've updated the version number in [`package.json`](./package.json) AND [`src/cs.ts`](./src/cs.ts).
12+
13+
## Publishing Changes
14+
15+
1. `vsce package`
16+
2. `vsce publish`
17+
3. `ovsx publish <latest .vsix> -p <Open VSX token>`

0 commit comments

Comments
 (0)