search

labring / laf

Laf is a vibrant cloud development platform that provides essential tools like cloud functions, databases, and storage solutions. It enables developers to quickly unleash their creativity and bring innovative ideas to life with ease.
https://laf.dev
Apache License 2.0
7.22k stars 662 forks source link

I have been using laf for a while, here are some suggestions about laf #1177

Closed yxxchange closed 1 year ago

yxxchange commented 1 year ago

Search before asking

Feature Request

First，The log page of laf lacks refresh buttons like storage pages and database pages, which brings a bad experience. When I debug the program, I may need to test both the backend and laf at the same time. In this way, if I view the history log of laf, I have to keep refreshing the page to display the latest log. However, once this is done, there is a certain chance that the test cases on laf will be refreshed, so I have to re-enter the parameters.

Second，when I test my program on laf page, I often report the following errors： AxiosError: Request failed with status code 400. What is puzzling is that once this problem starts to appear, the way to solve it is often to modify the HTTP message. I can guarantee the correctness of my http message. Generally speaking, this problem occurs in the process of repeated testing of a same message.

Third, I feel that Laf lacks classification management and protection for user-developed functions. In my scenario, some functions are only used by developers for updating database information or generating keys. They are not meant to be accessed by external users. I suggest implementing a folder-like system for users to categorize their functions as needed. Additionally, there should be a protection mechanism to prevent accidental modifications or deletions of mature functions. The current deletion process is too simple and prone to accidents. These improvements would provide better function management and security in Laf.

Lastly, I believe that Laf's most crucial interfaces for users are HTTP-related and database-related APIs. However, I find that the documentation for the HTTP part is insufficient. Additionally, the performance of AI assistants like FastGPT, which provide support in this area, is not satisfactory when it comes to production-level requirements. They often provide non-functioning functions and their explanations of certain APIs are frequently self-contradictory. It would be beneficial to enhance the documentation for network-related API usage and provide specific explanations for Laf's unique APIs using specialized AI.

Are you willing to submit PR?

maslow commented 1 year ago

Thanks for your suggestions, we have fixed many bugs and improved expirences these days.

AxiosError: Request failed with status code 400. Still need more information about this issues.