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
This approach has limitations, particularly when Navbar or similar components are not present within the project. It requires all components to be known and available at compile-time, reducing flexibility.
Describe the solution you'd like
My idea is to import the file from a string and pass it, enabling the dynamic import of components. If this is not viable, an alternative solution should be implemented to allow using files from outside of the current project.
Under the hood, this string would be used to resolve and import the corresponding component dynamically, potentially using a method like import() or a custom resolver function.
Additional context
This feature would increase flexibility and modularity, allowing components to be loaded from external sources or repositories.
It could leverage existing dynamic import capabilities in JavaScript (e.g., import() function) or involve setting up a custom resolver within the framework.
Consideration should be given to error handling for cases where the component is not found or fails to load.
Let me know if you need any more adjustments or additional details.
The text was updated successfully, but these errors were encountered:
Certainly! Here is the updated feature request with your additional input, formatted in Markdown:
Feature Request: Dynamic Component Importing
Is your feature request related to a problem? Please describe.
Currently, to use a component like
Navbar
, we need to import it explicitly using a standard import statement:This approach has limitations, particularly when
Navbar
or similar components are not present within the project. It requires all components to be known and available at compile-time, reducing flexibility.Describe the solution you'd like
My idea is to import the file from a string and pass it, enabling the dynamic import of components. If this is not viable, an alternative solution should be implemented to allow using files from outside of the current project.
Example:
Under the hood, this string would be used to resolve and import the corresponding component dynamically, potentially using a method like
import()
or a custom resolver function.Additional context
import()
function) or involve setting up a custom resolver within the framework.Let me know if you need any more adjustments or additional details.
The text was updated successfully, but these errors were encountered: