Skip to content
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

data hierarchy #213

Open
hamedpro opened this issue Jul 14, 2023 · 2 comments
Open

data hierarchy #213

hamedpro opened this issue Jul 14, 2023 · 2 comments
Labels
frontend just helping developers find what they're more likely be able to do

Comments

@hamedpro
Copy link
Owner

think well about a tool or something making it easier to make sure everywhere that its required to consider parents or children of something they are considered. for example we want to show time line of a pack. do we need to show timelines of its children recursively ? even if we put an option to handle this particular situation there will also other places we face this decision.

@hamedpro hamedpro added the frontend just helping developers find what they're more likely be able to do label Jul 14, 2023
@hamedpro hamedpro modified the milestone: v1 Jul 14, 2023
@hamedpro
Copy link
Owner Author

add a new getter to cache_item s : children (number[]). in these situations we say something is a child of another thing :

  • a message is a child of what it belongs to.
  • a unit is children of its parent pack.

@hamedpro
Copy link
Owner Author

parts we need to make sure about them :

  • showing changes of children recursively in timeline of a parent
  • showing messages of children and so on inside the parent's messages
  • when navigating back in a Thing (back button takes you to its parent not home)
  • maybe there be other parts

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
frontend just helping developers find what they're more likely be able to do
Projects
Development

No branches or pull requests

1 participant