[PR #4782] chore: type option cell data trait cleanup #14851

Closed
opened 2026-03-24 21:51:09 +00:00 by mirror · 0 comments
Owner

Original Pull Request: https://github.com/AppFlowy-IO/AppFlowy/pull/4782

State: closed
Merged: Yes


  • TypeCellData is dead code. We use AnyMaps for serialization and deserialization when dealing with data storage and BoxAnys for generic in-memory storage instead now.
  • The DecodedCellData trait has been replaced with TypeOptionCellData whose contents are the same but is more thoroughly implemented (and actively used, in TypeOptionCellDataCompare)
  • FromCellString isn't required for the TypeOption::CellData type. We have replaced it with for<'a> From<&'a Cell>. As such, I've decided to remove this trait completely and let the individual cell data types that need this functionality implement the FromStr trait

Feature Preview


PR Checklist

  • My code adheres to AppFlowy's Conventions
  • I've listed at least one issue that this PR fixes in the description above.
  • I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes.
  • All existing tests are passing.
**Original Pull Request:** https://github.com/AppFlowy-IO/AppFlowy/pull/4782 **State:** closed **Merged:** Yes --- - `TypeCellData` is dead code. We use `AnyMap`s for serialization and deserialization when dealing with data storage and `BoxAny`s for generic in-memory storage instead now. - The `DecodedCellData` trait has been replaced with `TypeOptionCellData` whose contents are the same but is more thoroughly implemented (and actively used, in `TypeOptionCellDataCompare`) - `FromCellString` isn't required for the `TypeOption::CellData` type. We have replaced it with `for<'a> From<&'a Cell>`. As such, I've decided to remove this trait completely and let the individual cell data types that need this functionality implement the `FromStr` trait ### Feature Preview <!--- List at least one issue here that this PR addresses. If it fixes the issue, please use the [fixes](https://docs.github.com/en/get-started/writing-on-github/working-with-advanced-formatting/using-keywords-in-issues-and-pull-requests) keyword to close the issue. For example: fixes https://github.com/AppFlowy-IO/AppFlowy/pull/2106 --> --- <!--- Before you mark this PR ready for review, run through this checklist! --> #### PR Checklist - [ ] My code adheres to [AppFlowy's Conventions](https://docs.appflowy.io/docs/documentation/software-contributions/conventions) - [ ] I've listed at least one issue that this PR fixes in the description above. - [ ] I've added a test(s) to validate changes in this PR, or this PR only contains semantic changes. - [ ] All existing tests are passing.
mirror 2026-03-24 21:51:09 +00:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
AppFlowy-IO/AppFlowy#14851
No description provided.