e2corporation commented on issue #2826: URL: https://github.com/apache/incubator-devlake/issues/2826#issuecomment-1228392861
@likyh Before getting carried away with "Dynamic" everything, lets look at the problem you're trying to solve for. It sounds like the backend team as a whole has this anxiety of not knowing what needs to be done on Frontend's Config-UI when a new provider is added. You continue to make it sound like it's difficult to configure a Provider on UI when there's way more work in actually writing a backend plugin. The connection form is **already dynamic.** and it's a single unified form for All providers, it's driven by frontend's Integrations configuration as you are already aware of. If we wanted to use a completely separate connection form design for a provider type we already have the flexibility to do that. 1) Identify and Document Provider Registration Steps on UI (I will draft notes on this) 2) Optimize and Streamline the current Configuration Process 3) Evaluate the need for API Driven Dynamic Form controls The switch statements you mentioned I plan to consolidate into one callback that sets all unified connection props regardless of provider type. Let's look at the last TAPD PR 2675 for UI by @warren830 to get an idea of configuration changes needed on UI, https://github.com/apache/incubator-devlake/pull/2675 -- 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: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
