chore(wavesyncdb): bump to 0.6.0#56
Merged
Merged
Conversation
Breaking changes since 0.5.0 that warrant the minor bump under pre-1.0 semver: - `wavesyncdb::dioxus::use_synced_table` signature changed on both targets — it now takes a `SyncHandle` and a `SyncedTableEntity` type parameter instead of the per-backend `(WaveSyncDb)` / `(client, table)` argument shapes. The old behavior remains available behind `use_synced_table_db` (native) and `use_synced_table_client` (web). - `#[derive(SyncEntity)]` now requires `#[sea_orm(table_name = "...")]` at the struct level on all targets — the derive reads it to populate `SyncedTableEntity::table_name()`. Existing native users already satisfy this via `DeriveEntityModel`; wasm-only entities (added in this release) need it explicitly. Additive changes that don't break anything but expand the surface: - `BrowserEntity` is now auto-derived from `#[derive(SyncEntity)]` on wasm — manual impls still compile and are documented as the escape hatch for fields that can't round-trip through `serde_json::Value`. - New `SyncHandle` transport facade with cross-target `submit::<E>` for one-line writes. - `SyncedTableEntity` trait + its derive emission.
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.
Minor bump under pre-1.0 semver for the breaking changes that just landed in #55.
Breaking
wavesyncdb::dioxus::use_synced_tablesignature changed on both targets — it now takes aSyncHandleand aSyncedTableEntitytype parameter instead of the per-backend(WaveSyncDb)/(client, table)argument shapes. Old behavior is still available behinduse_synced_table_db(native) anduse_synced_table_client(web).#[derive(SyncEntity)]now requires#[sea_orm(table_name = "...")]at the struct level on all targets. Existing native users already satisfy this viaDeriveEntityModel; wasm-only entities (added in this release) need it explicitly.Additive
BrowserEntityauto-derived from#[derive(SyncEntity)]on wasm.SyncHandlecross-target transport facade withsubmit::<E>(&entity).SyncedTableEntitymetadata trait.Test plan
cargo build -p wavesyncdb— version compiles