[GitHub] [incubator-devlake] tk103331 commented on pull request #2886: feat: setup configuration-ui plugin registry `Draft`

[GitBox <gi...@apache.org>]

tk103331 commented on PR #2886:
URL: https://github.com/apache/incubator-devlake/pull/2886#issuecomment-1234971523

   Sorry, I didn't see what you edited in my reply two days ago.
   
   > I do see your point, I wouldn't say it's scattered, sorting of the fields is not something needed or relevant, the order of the fields in the connection form follows a natural order starting with Name, ending with Rate Limit.
   
   What I mean is to spread the multiple information (name, label, placeholder) of a field to be defined in multiple places instead of using only one object.
   Regarding field sorting, in general, we will use the code writing order. However, if fileds is data requested from the backend. Possibly, the backend may use the map data structure (because the field is not fixed and cannot use struct), which will cause problems due to the uncertainty of the map traversal order. Of course, we can provide some instructions or helpers to avoid this problem, but it really depends on how the backend people write the code.
   
   > I see the point, and we can certainly evolve the configuration to let validation rules be defined here but it's not needed right now. Instead of showType we would just use type (string|number|object) etc and add a component prop to specify a form control that's to be used for render.
   
   Yes, the name `component` would be more appropriate, the name showType is a premature suggestion.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: commits-unsubscribe@devlake.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org