-
Notifications
You must be signed in to change notification settings - Fork 3
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
Feat: add platforms to hardware column #859
base: main
Are you sure you want to change the base?
Conversation
8e11ebb
to
d59981a
Compare
Added enviroment_misc.platform as a fallback case for the hardware column. When environment_compatible is null/undefined it will use the platform of the test if available Part of #854
Added enviroment_misc.platform as a fallback case for the hardware column. When environment_compatible is null/undefined it will use the platform of the test if available Closes #854
d59981a
to
589e34d
Compare
: misc?.platform | ||
? [misc?.platform] | ||
: undefined; |
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 is pretty much the same as misc?.platform
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.
misc?.platform
is type string | undefined
and I need the result to be string[] | undefined
. Doing only [misc?.platform]
, wouldn't work as well because that would be type (string | undefined)[]
]; | ||
import { buildHardwareArray } from '@/utils/table'; | ||
|
||
import { defaultColumns } from './DefaultBootsColumns'; |
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 is pretty much no gain moving to another file it will be only used in a single place
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.
I was following the same structure that was done to TestsTable
but it makes sense, I'll change it back
environment_misc.platform
as a fallback to hardware whenenvironment_compatible
is fullCloses #854
Important: In the current form boots table is showing the hardware column in the hardware details page but tests table is not. Should hardware column be added to the tests table, should it be removed from the boots table or should I keep it like it is already?