-
Notifications
You must be signed in to change notification settings - Fork 896
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
Reports: remove need to declare includes #13675
Reports: remove need to declare includes #13675
Conversation
0537618
to
1705f39
Compare
This pull request is not mergeable. Please rebase and repush. |
1705f39
to
c2895b7
Compare
Looks good to me. Are there any impacts on the report editor? Guess there might be if we load a report w/o the includes. |
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.
👍
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.
@lpichler Just double checking custom attributes with you. Pretty sure they are in cols and not includes but wanted to double check.
Yes, that's true. I am doing it in special method. (I'll check whether I can revamp it with your stuff)
@martinpovolny thanks. good eye. I'm guessing |
This pull request is not mergeable. Please rebase and repush. |
c2895b7
to
3af1aeb
Compare
Checked commits kbrock/manageiq@400581d~...3af1aeb with ruby 2.2.6, rubocop 0.47.1, and haml-lint 0.20.0 |
@martinpovolny Regarding the report editor |
NOTE: reverting these report changes in #14439 - |
Blocked:
For reports, the columns are stated 2 times:
includes
which defines the joined table columns.cols
which defines the database columns in the base table.sort_cols
which defines the joined table columns and the base table columns, and this is ordered.This change focuses on the unnecessary
includes
. If the value is missing, the report simply derives the value fromsort_cols
.The long term goal is to just specify the columns once (i.e.
sort_cols
) and not requireincludes
orcols
. (they would be supported, just not required) This will simplify extracting metadata from reports.@lpichler Just double checking custom attributes with you. Pretty sure they are in
cols
and notincludes
but wanted to double check.