Tracking: View Component V3

[BlakeWilliams]

This issue is for tracking the work required to get the library ready for a V3 release! If you have thoughts or feedback that is relevant to the V3 release (such as breaking changes), please comment here or open an issue referencing this issue.

Goals

• Components + View Colocation (Moving components to app/views)
• Add a caching API for view-components
• Documentation modernization (site)
• Add YARD documentation #473
• Deprecate Content Areas #620
• Deprecate Slots V1 and promote Slots V2 to a default feature of components
• Project-wide config for generators #623
• Add with_content API
• CSS encapsulation
• New slot setter/getter API (for with_content compatibility) Add separate slot getter/setter API proposal #1262
• Include Translations support by default #1042
• Add paved path for unit testing components with behaviors #904
• Breaking change Revert counter to start at 0 instead of 1 #361
• Remove rendered_component Restore rendered_component, deprecate for v3 #1380
• Turn on render_preview by default
• Add better test examples around rendered_content vs. page to make sure the latter is viable
• Strip whitespace from templates by default Strip trailing whitespace in templates #1379
• Deprecate support of Ruby < 2.7
• Move repo to separate org
• Clarify EOL policy for Rails dependency

Communication

• Share with contact at Ruby Weekly
• Publish on Rubyland news
• Internal engineering-wide post

[jesster2k10]

Hey, I'm interested in seeing how the CSS Encapsulation would look like. Are there any ideas so far?

[Spone]

Hey, I'm interested in seeing how the CSS Encapsulation would look like. Are there any ideas so far?

Hi @jesster2k10 here is the related PR: #677

[BlakeWilliams]

@boardfish 👋 just a heads-up, but we're hoping to finalize v3 around April 2022 that will include your work on the generators.

[BlakeWilliams]

also cc @elia and @franks921, I added two items that have you assigned as owners. No pressure though, we're happy to help out where we can with that work.

[frank-who]

also cc @elia and @franks921, I added two items that have you assigned as owners. No pressure though, we're happy to help out where we can with that work.

Hi @BlakeWilliams

Unfortunately, I'm still working through a heavy workload and my time is limited. I should be able to have a look in the next 2 weeks or so. Apologies if this is causing any delays

[BlakeWilliams]

Unfortunately, I'm still working through a heavy workload and my time is limited. I should be able to have a look in the next 2 weeks or so. Apologies if this is causing any delays

Not at all, and like I said, no pressure! If you won't be able to get to it let us know, not a big deal at all. 🙂

[elia]

@BlakeWilliams just out of curiosity, any reason we're a tracking issue instead of a milestone (or both)?

[Spone]

@elia @BlakeWilliams I'd be happy to convert this to a milestone if you think it's a good idea. In my opinion it would make things clearer :)

[joelhawksley]

@elia @Spone we generally just use tracking issues for this kind of thing internally ❤️