Skip to content

Feat/api refactor #263

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

Merged
merged 7 commits into from
Sep 2, 2024
Merged

Feat/api refactor #263

merged 7 commits into from
Sep 2, 2024

Conversation

plutoless
Copy link
Contributor

No description provided.

Copy link
Collaborator

@wangyoucao577 wangyoucao577 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What's the main purpose for this refactoring? Any problem to solve?

@plutoless
Copy link
Contributor Author

What's the main purpose for this refactoring? Any problem to solve?

  1. move graph logic to front end service, instead of doing it in front-ui on browser
  2. provide core agent mgmt apis and docs, so that api can be used without ui
  3. add inifinity timeout option when starting worker, so it's easier for developers who starts agent w/o ui (he does not need to keep pinging)

@plutoless plutoless merged commit 56d3b8e into main Sep 2, 2024
5 checks passed
@plutoless plutoless deleted the feat/api-refactor branch September 2, 2024 17:34
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants