DAG of Flowlets instead of Tree of Flowlets

Open
#84 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
typescript
Domain
tooling

Research direction

Start by locating the TypeScript Flowlet class and reading how its current tree relationships are represented and consumed. Investigate the existing flow construction and traversal entry points to determine whether joining multiple flowlets is supported; done requires an agreed DAG design and corresponding behavior, but the issue names no tests or concrete acceptance criteria.

Written by the indexing model from the issue text.

Description

should we support flowlets as a DAG instead of tree.

There might be cases that a flowlet is the join point of multiple other flowlets. For example, if we have batching mechanism that "merges" multiple flows into one, we might want to represent a new flowlet for the batched activity that summarizes the incoming flowlets.

We can potentially support this model by adding an optional readonly parents?: Flowlet[] to the Flowlet class. That way, we can handle the flow as a DAG instead of a tree.

Dominant language
TypeScript
Stars
47
Forks
33
Avg merge
18h 27m
Merged PRs (30d)
1

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from facebook/hyperion

All issues in facebook/hyperion

Similar issues

More TypeScript issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.