ViewComponent v4

[camertron]

Potential ideas for v4 of the framework

• Replace helpers with explicit api in v4 #1848
• Migrate #content to be a slot #1974
• Re-work slots, potentially remove Slot wrapper?
• Stop inheriting from ActionView::Base?
• Add inline template option to generator #1792
• Remove support for unsupported versions of ruby and rails #1898
• Migrate ViewComponent::Base.format to return a format instead of the variant #1973

[reeganviljoen]

@camertron can we please consider adding #1898 to this list

[collimarco]

Can we please also consider to add helpers to provide a short, compact syntax that is easier to write / read (syntactic sugar)?

https://answers.abstractbrain.com/using-rails-helpers-x-component-for-rendering-viewcomponents

The helpers would be an addition, they don't remove the traditional way, if you want to keep using it. I think that they are aligned with the Rails philosophy and are similar to the Rails view helpers and Rails routing helpers.

[BlakeWilliams]

@collimarco That's not something we're targeting for a potential v4 release at the moment given the past discussion and identified trade-offs. If you or others feel passionate about it, I'd recommend creating a gem to help prove out the value and demand of that functionality to make a case for upstreaming.

[collimarco]

@BlakeWilliams Ok, thanks for the reply. Would you mind pointing me to the discussion with the "identified trade-offs"? This is the only issue that I found, but it seems that the downsides listed there have been resolved.

[reeganviljoen]

@camertron @joelhawksley @boardfish @BlakeWilliams (sorry If I left anyone out) I have been thinking about #1848 and I thought maybe adding a config that disables the use of helpers through helpers.<helper_name> and forces you to use use_helpers <helper_name> when you need helpers

Maybe config.view_component.use_strict_helpers = true

This can help in developers that wish to make it easier to reason when using global state as is the intention with #1848

If you have any thoughts please let me know, so I know if i should pursue this in a separate issue

[reeganviljoen]

@camertron @joelhawksley @boardfish @BlakeWilliams (sorry If I left anyone out) I have been thinking about #1848 and I thought maybe adding a config that disables the use of helpers through helpers.<helper_name> and forces you to use use_helpers <helper_name> when you need helpers

Maybe config.view_component.use_strict_helpers = true

This can help in developers that wish to make it easier to reason when using global state as is the intention with #1848

If you have any thoughts please let me know, so I know if i should pursue this in a separate issue

I have made this its own issue in #1976

[anthonyshchang]

https://github.com/ViewComponent/view_component/blob/v2.83.0/view_component.gemspec#L32

that activesupport dep breaks when upgrading to rails 8, so could we also ensure that v4 supports that?

[rmacklin]

You linked to v2.83.0 - v3 already supports rails 8.0:

view_component/view_component.gemspec

Line 32 in 644bfb7

spec.add_runtime_dependency "activesupport", [">= 5.2.0", "< 8.1"]

so it will definitely remain supported in v4

[joelhawksley]

Closing in favor of #2085.