Open sselvam7 opened 1 month ago
@sselvam7 could you tell us a bit about the components you want to use from your internal artifacts and why?
@Nikhil-Nandagopal Sure. We have a canvas component that is used to display a json in a specific way in multiple places across the UI of the product. Now we are looking at creating an internal tool for support who need the ability to look up same information from the support tool. We push all the components to a central internal artifactory. Now, if we want to use that component in the support tool, our options are 1) make the component publicly available via jsdelivr which is not possible for us or 2) possibly copy paste the entire canvas component in appsmith and maintain it in two separate places. If not, our only option is to show the raw data for support admin.
Fetching from internal artifactory would help us to push the same canvas and use the same canvas component in public UI and also support tool. Please let me know if you need any other clarifications.
Hey @sselvam7, I want to make sure that I understand your use case correctly.
We push all the components to a central internal artifactory.
Are these react components that you've created? (similar to ImageGallery
in our custom widgets doc)
2) possibly copy paste the entire canvas component in appsmith and maintain it in two separate places.
Please elaborate on this. Are you talking about the core component that you want to reuse or custom widgets' implementation logic.
From what I've understood, you are requesting reusability for custom widgets, which unfortunately right now is tedious copy-paste OR export only.
Is there an existing issue for this?
Summary
Currently, a lot of components in our organization are pushed to an internal artifactory and it gets reused across the organization. As per custom widgets doc, it is only possible to use components that can be made available publicly via jsdelivr or UNPKG. This limits the use of Custom Widgets since the components that we want to use are not allowed to be made available publicly. This would be a huge game changer for our adoption to AppSmith.
Why should this be worked on?