Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Setting which modules can pass context values outside of config #700

Open
Zurga opened this issue Jul 22, 2023 · 0 comments
Open

Setting which modules can pass context values outside of config #700

Zurga opened this issue Jul 22, 2023 · 0 comments

Comments

@Zurga
Copy link
Contributor

Zurga commented Jul 22, 2023

Currently, SurfaceBulma uses contexts to pass variable class names to components in slots. This works great and allows the user to use components with flexibility. A Link used inside a Navbar will have the correct class set without the user thinking about it.

However, due to the fact that allowing a component to do this is set in the config, the user of SurfaceBulma has to either manually add this, or add import_config ../deps/surface_buma/config/contexts to their own config.

Although this is not a hurdle that cannot be overcome, for the sake of ease of use, it would be nice if there was another way to configure this setting.

Maybe there is an undocumented way that I have missed, but setting @propagate_context_to_slots_map directly on a Component does get rid of the warning, but the values are not passed on to the slot.

@Zurga Zurga changed the title Setting which modules can pass context values through slots at module level Setting which modules can pass context values outside of config Jul 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant