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

Undeprecate :class_name #2697

Merged
merged 1 commit into from
Nov 4, 2024

Conversation

pablobm
Copy link
Collaborator

@pablobm pablobm commented Oct 26, 2024

If we are going towards v1.0.0, perhaps we should undeprecate :class_name 😄

At #2384 and #2546, we have seen legitimate use cases for this option, so perhaps it should be back on the menu after all.

I'm not clear yet about the other deprecations that came with it though: :foreign_key and :primary_key. I think those might be ok? Has anyone come across use cases for them? Perhaps @littleforest?

While updating the documentation, I realised there's an example that uses :class_name and doesn't need it, so I have addressed it.

Copy link
Member

@nickcharlton nickcharlton left a comment

Choose a reason for hiding this comment

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

Looks good!

We tried to remove `:class_name` (along with some others), as it didn't
seem like they had a legitimate use as of thoughtbot#2384 and thoughtbot#2546. But we've
been seeing various cases where it's still helpful to have.

Closes thoughtbot#2384.
@nickcharlton nickcharlton force-pushed the undeprecate-class-name branch from 0b2e519 to ac89843 Compare November 4, 2024 13:01
@nickcharlton nickcharlton merged commit f9c5f1a into thoughtbot:main Nov 4, 2024
10 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants