TEN-framework / TEN-framework/ten-framework
[BUG] Refactor add/remove connection api in TMAN designer backend
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 11.1k
- Forks
- 1.4k
- Avg merge
- 2d 15m
- Merged PRs (30d)
- 22
Description
With the addition of many syntactic sugars to TEN graph, such as names, selector, reversed_connection, etc., the previous tman designer would flatten the graph and provide the flattened version to the frontend for display and modification.
Now, after a series of adaptations, the frontend can display complex graphs, but adding or deleting connections is not yet supported.
This requires the tman designer backend to modify the API protocol and be able to operate directly on the graph before flattening.
The request payload can be modified as following:
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing the tman designer backend's connection add/remove API and the graph-flattening path described in the issue. Compare the existing request payload with the proposed payloads, then verify that connection changes operate on the complex graph before flattening and remain displayable by the frontend.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, backend, backend-api-design
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100