New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore(merge-tree sequence examples): remove NestBegin and NestEnd reference types #17546
chore(merge-tree sequence examples): remove NestBegin and NestEnd reference types #17546
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
For prosemirror, the example seems good enough if we just do some finagling with the reference types. That said, it's not clear to me which reference type these should switch to, and the APIs being used appear quite old. I'm not sure if we want to remove this example entirely.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
shared-text uses a lot of merge-tree internals, and it seems best just to delete entirely.
| if (refHasTileLabels(lref)) { | ||
| this.hierRefCount++; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I kept hierRefCount and the tiles stuff around as I wasn't sure if they were safe to remove.
| } | ||
|
|
||
| public hierBlock() { | ||
| return this; | ||
| } | ||
|
|
||
| public hierToString(indentCount: number) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This didn't seem to have any usage anywhere
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
See also: 9dc1859
i'm ~intending to revert this change, but for now the webflow build seems quite broken and i want to see the test run results in CI
⯆ @fluid-example/bundle-size-tests: -5.9 KB
Baseline commit: 550e869 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we need to do some deprecations in main for completeness, but i highly doubt any of this is in use. we also need a changeset here to call out the removals in mergetree/seq, keep it brief, as again, i don't think its used, as this stuff probably doesn't work anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
actually, can we bring back web flow and test farm, feel free to rip features out, but i'd like to keep both. might make sense to do this with the deprecations in main
|
testFarm wasn't deleted in this PR, it just has a lot of lines deleted. I did delete it in #17547, however. |
This reverts commit 61e4d8b.
|
Deprecation PR: #17555 |
| @@ -577,8 +577,7 @@ export function createSequenceInterval( | |||
| endRefType = ReferenceType.Transient; | |||
| } else { | |||
| if (intervalType === IntervalType.Nest) { | |||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i think we should also deprecate IntervalType.Nest
|
This PR is ready to merge! Please review it and squash merge into |
This is a ~conservative first pass at removing some of the tech debt related to the
NestBeginandNestEndreference types. Alongside these enum variants, this change removesgetStackContext,RangeStackMap, theshared-textexample, and a few other things.I will add some review comments to call out some changes (or lack thereof) to make sure they make sense once CI is green.