Skip to content

Conversation

Eric-Guo
Copy link

What are you trying to accomplish?

Using new view_component version.

Integration

No need change code in production (open project)

List the issues that this change affects.

N/A

Risk Assessment

  • Low risk the change is small, highly observable, and easily rolled back.
  • Medium risk changes that are isolated, reduced in scope or could impact few users. The change will not impact library availability.
  • High risk changes are those that could impact customers and SLOs, low or no test coverage, low observability, or slow to rollback.

What approach did you choose and why?

I just run the test in my MacBook M4 Pro and don't want install too many view_component versions.

Anything you want to highlight for special attention from reviewers?

Nothing.

Accessibility

Not relative

Merge checklist

  • Not added/updated tests
  • Not added/updated documentation
  • Not added/updated previews (Lookbook)
  • Tested in Chrome
  • Not tested in Firefox
  • Tested in Safari
  • Not tested in Edge

Copy link

changeset-bot bot commented Aug 30, 2025

⚠️ No Changeset found

Latest commit: f0fa589

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

render partial: "primer/view_components/auto_check/error_message",
locals: { input_value: params[:value] },
status: :unprocessable_entity,
status: :unprocessable_content,
Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

It's warning and suggested by Rails 8.0.2

@Eric-Guo Eric-Guo force-pushed the bump_view_component branch from 57c65d0 to 6623e60 Compare August 30, 2025 02:37
@HDinger
Copy link
Collaborator

HDinger commented Sep 17, 2025

Hi @Eric-Guo

Thanks for this PR. The primer people have updated to 4.0.2 by now as well, which is why we have some conflicts here. With regards to the change of the status code, do you mind providing that change upstream as well? I am pretty sure, that they will accept that as well and it would be could to have the repos in sync..

@Eric-Guo
Copy link
Author

No problem, in fact @thape-cn is already running 4.0.2 at least 2 weeks.

There is only three place need to change, maybe you would like change yourself?

I'm also OK to propose a PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants