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

follow RESTful API #42

Open
himself65 opened this issue Sep 6, 2022 · 3 comments
Open

follow RESTful API #42

himself65 opened this issue Sep 6, 2022 · 3 comments

Comments

@himself65
Copy link
Contributor

himself65 commented Sep 6, 2022

make GET /list to GET /
make GET /param/{id} to GET /{id}
make POST /call/{id} to POST /{id}

@TURX
Copy link
Collaborator

TURX commented Sep 6, 2022

They are /param{PATH} and /call/{id}, which are different. Still need to merge to GET and POST?

@himself65
Copy link
Contributor Author

Yes, the reason is we will make a single user function into a serverless-like function, so each function path should handle all cases requested by client

@himself65
Copy link
Contributor Author

Please add this feature to the dev branch. Let me try the stability of this

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

No branches or pull requests

2 participants