Comments (10)
For anyone following along PVH's comments above are a list of things we talked about synchronously as being important for a release. I've created issues for most of them and added them to the tracking issue. With the exception of
mergeText
- change/patch confusiong
- BroadcastChannel breaks ephemeral data
We decided that since these can all be fixed in a backwards compatible manner and are low enough priority that we shouldn't block a release on them.
from automerge-repo.
One question is whether we should block this release on #87 . I think @acurrieclark presents a good argument in that issue that we should redesign our message types. We already have interoperable implementations in various states in Rust, Swift, and Kotlin. It would be nice if we could standardise our wire protocol before even more implementations pop up.
On the other hand, I want to get this release out fairly soon and this might be the kind of design task that expands surprisigngly. Maybe we should just add a version negotiation step so that we can solve this later? The tradeoff obviously being that then we might end up supporting the current protocol as a legacy protocol for a while? @pvh @HerbCaudill thoughts?
from automerge-repo.
So, sorry it took a bit to get back to you. I think this list is roughly correct. I would like to land @neftaly 's work on useAwareness and useBootstrap in here as well, but agree we should not block. I wanted to deal with 87 pre-1.0 but I feel at this point that it's not far enough along to commit to and just barely shy of being worth blocking a release (mostly due to uncertainty about what to do).
from automerge-repo.
@pvh has taken over #102 and I think is also blocked by #112
from automerge-repo.
#102 and #112 are now landed on main -- happy to try and get #45 landed too.
from automerge-repo.
Since @neftaly asked, the goal is to finish this list for a release in two weeks. That means ideally clearing the list out this week and then spending the following week fixing bugs / polishing / etc.
from automerge-repo.
Okay -- there are PRs up for all of these now in one form or another except #116. @alexjg would love your review of the small stuff; feel free to land where you're confident. I'm going to call it a night here.
from automerge-repo.
@alexjg Added a few issues for consideration for v1 following conversations with @pvh
from automerge-repo.
I suggest fixing #129 for 1.0
from automerge-repo.
@alexjg i think we could probably close this out?
from automerge-repo.
Related Issues (20)
- Repo Gets into a bad state when Automerge URLs are being requested simultaneously HOT 1
- Intermittent CI test failures
- NodeFSStorageAdapter lock exception on large number of updates. HOT 2
- An unavailable document may just not be found yet
- WebSocket Ready flag should only be set after Open event HOT 2
- Get latest changes as a document instead of a binary HOT 5
- Virus detected in github head! Windows Defender Trojan:Script/Wacatac.H!ml HOT 4
- WebSocket client disconnection
- Access to RawString through automerge-repo? HOT 1
- pnpm run dev, pnpm run dev:demo not working HOT 3
- Error: recursive use of an object detected which would lead to unsafe aliasing in rust HOT 4
- network sync protocol leaks documentIds to peers HOT 2
- [Svelte] Counter works but Text doesn't HOT 2
- On Peers in Automerge-Repo: Design HOT 2
- When a change event is emitted by the handle the `handle.docSync()` is still the old value HOT 5
- Large enough messages block the main thread for a long time, which can lead to socket timeouts on blocked clients HOT 3
- svelte: provide a way to await the document becoming ready HOT 1
- Repo and WebSocket provider send two responses for a "request" - the first unavailable, the second a sync HOT 1
- Share policy prevents fetching document from sync server
- repo.clone error message suggests using "handle.waitForReady", which doesn't exist
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from automerge-repo.