-
Notifications
You must be signed in to change notification settings - Fork 897
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
[WIP] Remove Category - use Classification instead #17210
Conversation
rubocop: currently |
3902ca6
to
5d83ba0
Compare
I didn't think we had a category model, so that's surprising. If it's phased out can we just delete the Category model in this PR...or is that a follow up once you verify other repos aren't using it? |
@Fryguy it is referenced in 3 other repos and factories. Will put in requests over there. Debating if it makes sense to transition Category -> Classification -> Tag. Or just do one fell swoop. |
3a974ad
to
a5a7466
Compare
I think Category -> Classification -> Tag makes sense. I think if this PR removed Category that would be a good step 1. |
This LGTM, but have you tested the other repos, particularly manageiq-ui-classic to see that there are no failures? |
This pull request is not mergeable. Please rebase and repush. |
LOL, never knew we had a Category model. But but... this table has no STI Let me know if I can help 🔥 ✂️ 😄 |
let(:dynamic) { false } | ||
let(:category) do | ||
double("Category", :name => "best category ever", :description => "best category ever", :single_value => true) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This makes me laugh
Agreed.
Same here. |
@kbrock Is this still in progress or should it be closed? Wasn't sure what you meant by
|
@Fryguy yea. so this has been pared back so much. This is as far as I feel comfortable going with this PR. Not ready to drop If you don't like, then we can just close/toss. |
WIP status: Looks like we have a few strings passed around with Category objects. the |
This pull request is not mergeable. Please rebase and repush. |
Checked commit kbrock@4d4b680 with ruby 2.3.3, rubocop 0.52.1, haml-lint 0.20.0, and yamllint 1.10.0 app/models/dialog_field_importer.rb
|
Category was added to simplify the api. It really isn't hurting anyone, especially since we can use a named scope in here and not reference closing |
The high level goal is to have tags that are hierarchy aware.
So we will merge
Classification
andCategory
intoTag
.Since
Category < Classification
, this PR takes an easy step and removesCategory
./cc @jrafanie @Fryguy any opinions?