You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
We are trying to build new navigational item. It will look like other navigational items (recent-files, shared, favorites,..) but with different search criteria. For this we have to use many existing components in ACA like PageComponent, PreviewComponent. So we have to write these new custom components in ACA instead of extensions library. We need to modularize all these components so that we can use them in extension libraries. Describe the solution you'd like
We need to keep all reusable modules to be moved as separate libraries so that we can reuse them in extension libraries. Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Document list with all the features is the common feature we use to develop new components. Its ideal all the preview/ page components / and any other components related to this will be part of separate library to reuse in the custom extensions library.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
We are trying to build new navigational item. It will look like other navigational items (recent-files, shared, favorites,..) but with different search criteria. For this we have to use many existing components in ACA like PageComponent, PreviewComponent. So we have to write these new custom components in ACA instead of extensions library. We need to modularize all these components so that we can use them in extension libraries.
Describe the solution you'd like
We need to keep all reusable modules to be moved as separate libraries so that we can reuse them in extension libraries.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Document list with all the features is the common feature we use to develop new components. Its ideal all the preview/ page components / and any other components related to this will be part of separate library to reuse in the custom extensions library.
The text was updated successfully, but these errors were encountered: