Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
1.0.0: Should we deprecate Fossil Delta?
See original GitHub issueIssue Description
Hey guys, as we’re moving towards 1.0.0 (~August maybe?), I’d like to reduce the complexity as much as possible on the next version that will contain breaking changes.
So I’d like to know if you’re okay with the deprecation of Fossil Delta?
I believe there’s nothing you can do with Fossil Delta that you cannot do with the Schema, and the strong types with it play much nicely with C# and other languages.
Feel free to suggest if you’d like to see improvements on how to use the Schema.
👍 DEPRECATE Fossil Delta on 1.0.0
👎 SUPPORT Fossil Delta on 1.0.0
Issue Analytics
- State:
- Created 4 years ago
- Reactions:47
- Comments:5
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
I’m fine with deprecating Fossil Delta but consider doing so only after all official clients have at least a stable support for Schema ex. the haxe client currently doesn’t support Schema
I prefer Fossil Delta but would be fine if it was easy to use as a third-party plugin. Don’t prefer the heavy-handed typeness and verbosity of the default serializer.