Repository navigation
chore(zero-swift): version packages - #15
Merged
Merged
Conversation
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 04:09
11dff60 to
a9ca717
Compare
github-actions
Bot
force-pushed
the
changeset-release/main
branch
from
October 22, 2026 06:24
a9ca717 to
3d80c9d
Compare
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.
This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and publish to npm yourself or setup this action to publish 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
zero-swift@0.4.0
Minor Changes
76312e4:
JSONValue.objectholds aJSONObjectinstead of a[String: JSONValue]. AJSONObjectkeeps its keys as a JS object does: integer-like keys first in ascending order, then the others in the order they were set, so JSON is written asJSON.stringifywrites it. Keys are compared by UTF-16 code unit, so keys that differ only in Unicode normalization ("é"and"e\u{301}") stay apart instead of one overwriting the other. Before, they merged in pokes (row values, primary keys, merges, client IDs), and custom-query and AST hashes of such keys differed from JS. Dictionary literals,object[key], andfor (key, value) in objectwork as before, andRow(_:)andRow.objectconvert both ways.Migration: where code builds
.object(dict)from a[String: JSONValue]variable, write.object(JSONObject(dict))or declare the variable asJSONObject.objectValueandZeroObjectReader.object/ZeroObjectWriter.objectare nowJSONObject; use.dictionarywhere a[String: JSONValue]is needed.AST.Bound.rowis aJSONObject, andAnyQuery.start,TableMutator, andLoopbackServer.puttake aJSONObjectas well as a dictionary.Patch Changes
Zeroinstances of one client group in one process (the same user,storageKey, and storage, such as two windows) no longer drop each other's queries:initConnectionlists every running client of the group inactiveClients, as in JS, so zero-cache doesn't delete the other one. When one closes, the others senddeleteClientsfor it once.<=and>=filters no longer matchNaN. Storage: every client sharing a database hears about a write failure, and a closed client doesn't; writes queued before a failure no longer land after it; a database busy past the busy timeout is retried by the next write instead of being a storage failure; a read failure loading the client group is reported throughonStorageFailureand moves the client to memory; and the memory fallback after a failed open is shared by name in the process, like.memory.codegengenerates Swift that compiles for any table, column, relationship, JSON field, or enumeration value name. A name that is taken, a keyword Swift doesn't allow even backticked, a member the generated code declares, or a type it uses is renamed by a documented rule, and keeps its original name in the schema,CodingKeys, and raw values. Names outside ASCII are kept where Swift allows them, enumeration values with control characters are escaped as Swift allows, and a recursivejson<T>()type isJSONValuewhere it recurs instead of overflowing the stack.