Klesh Wong
Klesh Wong
> Hi, @klesh, this is my plan. > > 1. Create a new directory `config-ui-lib`.(This directory contains all the development bases, and I have done this step). > 2. Create...
> @klesh > > 1. Yes. > 2. I need to think about it, maybe after finishing the first test I can give it. Yeah, sure. > 3. I don't...
However, it is quite confusing for users, they would get an unexpected result when they set the options to empty.
I added this to v0.15 and we should discuss this matter. @Startrekzky @yumengwang03
@e2corporation The intent of this feature is for Documentation's sake, we can't describe all plugins options in a single API endpoint `/blueprints` because options are plugin specific. As of config-ui,...
@keon94 Yeah, sure. The problem is we can not put JSON-Schema for all plugins to a "Framework" level API. We need to put them to "Plugin" level API endpoints
I agree, totally. @yumengwang03 @Startrekzky FYI
@keon94 It was unified as the following ```json { "success": true|false, "message": "errors" } ``` I think we should keep these 2 fields to maintain FE compatibility as well as...
Th problem seems to be fixed in main branch bf4de4df3bda079b4cca2ae9e97e8cc9e3d46c54 Close it for now
@nicoabie No, not really. It was chosen simply because it worked :joy:. Maybe we should put a link to https://github.com/vektra/mockery#installation instead of giving the `go install` method directly. What do...