Repository navigation
chore(release): 2.1.0 - #100
Merged
Merged
Conversation
- version 2.1.0, and the Unreleased changelog section dated as 2.1.0 - README: Workspace Notes and folders in the overview, the right-click menu instead of hover icons that no longer exist, the real setting names (`notes.`, and notesDefaultNoteExtension), "Command Palette", and search removed from future plans now that it exists - changelog: the 2.0.0 Changed heading was a level too high - .vscodeignore: leave .github and node_modules out of the package; the bundle only loads Node built-ins and vscode, and the one runtime dependency, vscode-uri, is only imported by an unused file
- src/viewProvider.ts was never imported; it was the only user of the vscode-uri dependency and of the mkdirp and rimraf type stubs in src/types - remove vscode-uri, @types/mkdirp, @types/rimraf, and @types/glob (glob 10 ships its own types); the extension now has no runtime dependencies - remove what the compiler reports as unused: extId, extPub and a Notes constructor nothing calls, the tree parameter of setupNotes, folderMap and folderPath in the tree provider, and the category and tags fields of tree items, which were never read
Rename Note, Delete Note, Rename Folder and Delete Folder act on the item they're run on, so from the command palette they had nothing to act on.
The screenshot was from 2020. The new one shows Workspace Notes above Notes, folders, and file icon theme icons, with sample notes.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Release 2.1.0. Everything since 2.0.0 adds features or fixes bugs, with no removals, so this is a minor version. The full list is in the CHANGELOG's 2.1.0 section.
Changes
package.jsonandpackage-lock.json, and the Unreleased changelog section dated as 2.1.0 (an empty Unreleased section stays above it).notes.notesLocation, notNotes.notesLocation, andnotesDefaultNoteExtension).vscodeignore:.githubandnode_modulesare left out of the package. The bundle only loads Node built-ins andvscode; the one runtime dependency,vscode-uri, is only imported bysrc/viewProvider.ts, which nothing imports.Also in this release
src/viewProvider.ts(never imported) and the type stubs only it used, thevscode-uridependency only it used,@types/glob(glob 10 ships its own types), and everything the compiler reports as unused (extId,extPub, aNotesconstructor nothing calls, an unused parameter,folderMap,folderPath, and the never-readcategoryandtagsfields on tree items). The extension now has no runtime dependencies.The package
vsce package(vsce 4.0.0 on Node 22) buildsvscode-notes-2.1.0.vsix: 31 files, 198 KB, with nonode_modules,.github, older.vsixfiles, source or tests. Its manifest says 2.1.0, and the bundle contains the new features.Installed into a clean VS Code 1.140 with
code --install-extension(no development path, extensions enabled), it showed asdionmunk.vscode-notes@2.1.0, displayed Workspace Notes above Notes, created a note from the List Notes search, and Search Notes found a note by its contents.After merging
v2.1.0and create the GitHub release with the 2.1.0 changelog section, attaching the.vsix.vsce publish(needs the publisher's access token) or by uploading the.vsix.