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

[ci skip]Docs highlight form_with over form_for #51704

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

notapatch
Copy link
Contributor

Motivation / Background

form_for has been soft-deprecated in favour of form_with.
However, the documentation outside of the Rails Guide does not show this change
and in the case of these changes it misses form_with completely.

Changes:

  • Adding form_with before form_for in documentation.
  • Replacing form_with with form_for in example code.
  • Editing to keep the lines within columns

Checklist

Before submitting the PR make sure the following are checked:

  • This Pull Request is related to one change. Unrelated changes should be opened in separate PRs.
  • Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: [Fix #issue-number]
  • Tests are added or updated if you fix a bug or add a feature.
  • CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.

form_for, and form_tag, have been soft-deprecated in favour of
form_with. However, the documentation outside of the Rails Guide
does not show this change often missing form_with completely.

This PR fixes that.

Changes:
- Adding form_with before form_for in text.
- Replacing form_with with form_for in example code.
@skipkayhil
Copy link
Member

It looks like this covers some of the same content as #50744. Let me get that merged first and then we can rebase this one

@notapatch
Copy link
Contributor Author

Thanks @skipkayhil !

Drat, should have checked! 🤦

I'll keep an eye out!

@notapatch
Copy link
Contributor Author

Hello @skipkayhil

(or other maintainers!)

Everything is looking good, but one decision is required:

The merged commit has removed all mention of form_for - whereas this PR kept both in (as form_for was soft-deprecated and not deprecated).

Do you want form_for to remain in the documentation like this PR or do you want it removed completely like the merged commit?

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

Successfully merging this pull request may close these issues.

None yet

2 participants