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
Using component 'icon' on the pro subdomain views resolves the ruby class IconComponent of ./frontend instead of ./frontend-pro. The _icon.html.slim partial is correctly resolved (using prepend_view_path as stated in your doc)
I guess I should not change Rails.application.config.komponent.component_paths using before_action in a "pro" controller since its shared between subdomains, and changing global config on each request seems dangerous.
I would like to avoid namespacing my entire 'pro' component directory like ./frontend-pro/components/pro/icon/_pro_icon.html.slim since it does not look clean.
What do you advise?
The text was updated successfully, but these errors were encountered:
Hi guys :) Hope you're fine !
First, thank you for this very nice gem.
I'm currently setting up Komponent 2.2.0 in our Rails app with subdomains and I would like to completely dissociate their frontends, let's say :
Problem : With 2 different komponent root directories, a conflict regarding the components ruby classes occurs because the modules have the same name.
Example for an "icon" component :
Using
component 'icon'
on the pro subdomain views resolves the ruby class IconComponent of./frontend
instead of./frontend-pro
. The_icon.html.slim
partial is correctly resolved (usingprepend_view_path
as stated in your doc)I guess I should not change
Rails.application.config.komponent.component_paths
usingbefore_action
in a "pro" controller since its shared between subdomains, and changing global config on each request seems dangerous.I would like to avoid namespacing my entire 'pro' component directory like
./frontend-pro/components/pro/icon/_pro_icon.html.slim
since it does not look clean.What do you advise?
The text was updated successfully, but these errors were encountered: