Version Packages - #964
Merged
Merged
Conversation
Deploying solid-primitives with
|
| Latest commit: |
dceab3a
|
| Status: | 🚫 Build failed. |
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
1 participant
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.
Releases
@solid-primitives/clipboard@1.6.5
Patch Changes
createClipboard'sdeferInitialparameter being completely non-functional —deferInitial || truealways evaluated totrueregardless of the argument passed, so explicitly passingdeferInitial={false}had no effect and the clipboard was never written from the initial signal value (resolves Clipboard deferInitial says the default is false but it is actually true #790). Also corrected the JSDoc, which incorrectly claimed the default wasfalsewhen the intended (and actual, once fixed) default istrue— skip the initial write unlessdeferInitialis explicitlyfalse.@solid-primitives/keyboard@1.3.6
Patch Changes
useKeyDownList(and everything built on it:useCurrentlyHeldKey,useKeyDownSequence,createKeyHold,createShortcut) failing to re-trigger on repeated presses of shortcuts involving theMetakey, e.g.["Meta", "P"]on macOS. macOS never fireskeyupfor other keys held down together with Meta, only for Meta itself, souseKeyDownListnow treats Meta'skeyupas a signal to clear all tracked keys, preventing stale key state from corrupting the next press.