v4.0.0

[joelhawksley]

This PR will contain the breaking changes to ship for v4.0.0. We're still likely a long way's off, but I wanted to start to collect changes we know we'll want to land here. Until decided otherwise, we plan to release v4 on or after April 1, 2025,

Tasks

Potentially breaking:

• Audit remaining open issues and discussions to make sure no other breaking changes are needed
• Migrate to local configuration, review all config options for possible removal
• Re-work slots, potentially remove Slot wrapper? (enables .with_slot.with_content)
• Validate all internal instance variables have __vc_ prefix

Cleanups:

• set rubygems_mfa_required
• Fully review all docs, including links to external references
• Add docs for configuration: Better configuration scaffolding #2188
• Reference ViewComponent fragment caching gem to see if anything should be upstreamed (https://github.com/patrickarnett/view_component-fragment_caching)
• Add layout attribute to Rails' render: Add layout attribute POC #2232
• Revisit docs generation
• Resolve PVC test suite warnings
• Revisit symlink used for RSPec tests to avoid duplicated test files in development searches
• audit for optimal usage of object shapes: Enable warning on shape too complex #2258
• Add docs for all public methods
• Make any experimental features included by default
• API docs should not be on main source control
• Revisit and document or remove nocovs
• Consider making RequestDetails in Rails public
• Revisit benchmarks to see if the VC benchmark is being done in dev mode
• Add trusted publishing: https://jcouball.substack.com/p/continuous-delivery-for-ruby-gems
• Extract dotcom VC compiler from GitHub.com (sorbet/tapioca/compilers/view_component.rb / lib/tasks/sorbet.rake)
• Revisit skipped tests
• Use mutant gem to find bugs
• Add rubycritic gem
• Consider using something like changesets for changelogs, or at least add better guidelines for writing changelogs
• Bundle audit / brakeman
• Set up RubyGems org for ViewComponent
• auto-generate contributor list?
• Add check for test changes for all functional PRs
• audit rubocop exceptions
• Audit/close open issues on repo

Done:

• Remove any references to v4, such as in the compiler.
• Include SlotableDefault by default
• Stop inheriting from ActionView::Base?
• Use single ActionView::Base instead of inheritance?
• Always enable capture patch? - test at GitHub, enable by default before v4, remove toggle in v4, could we do it locally in PVC instead? (use refinements?)
• Add inline template option to generator #1792
• Add note about v4 being a LTS release
• See about making internal constants private
• Follow up on Allow implicit locale in component file names #2118 with more robust solution
• Revisit view_component-contrib items
• Further restrict access to internal APIs: Underscore internal methods that are public #2100
• Migrate ViewComponent::Base.format to return a format instead of the variant #1973
• Should we remove RedefinedSlotError?
• consolidate ADRs into History
• Drop method_source / assets from previews and direct folks to Lookbook
• Search for “rails” and “6.1” etc to make sure we've removed all deprecatable paths
• Remove use of ruby2 keywords
• Revisit all dependencies to see if we still need them
• Update rspec-rails to v7
• Update turbo-rails to v2
• Set up CI for whatever release series we support (one previous major for security? document this, dropping security support for v2 in v4 release)
• Breaking change to compiler to simplify render path collisions
• Verify all respond_to? checks are still necessary