-
Notifications
You must be signed in to change notification settings - Fork 615
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
Improve nav item extensions #1584
Improve nav item extensions #1584
Conversation
|
||
const plugin: Plugin<ConsumedExtensions> = [ | ||
{ | ||
type: 'FeatureFlag/Model', |
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.
The reason for moving this extension up in the list is to highlight that each plugin should start with adding its own feature flag(s).
Other extensions like nav items should be gated by those feature flags.
componentProps: { | ||
name: 'Test ResourceCluster Link', | ||
resource: 'projects', | ||
required: [FLAGS.OPENSHIFT, 'TEST_MODEL_FLAG'], |
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 link is equivalent to
<ResourceClusterLink
resource="projects"
name="Test ResourceCluster Link"
required={[FLAGS.OPENSHIFT, 'TEST_MODEL_FLAG']}
/>
@jtomasek This addresses the issue of adding nav items to all known sections. |
This PR is based on #1528 (not merged yet) so the first commit isn't related to this PR. |
/retest |
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.
lgtm, we should rebase now that #1528 merged
} | ||
} | ||
|
||
export class ResourceNSLink extends NavLink<ResourceNSLinkProps> { |
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.
Not new, but I'd like to get away from using inheritance in the nav components. Not necessary for this PR, just an observation.
I'm on it. |
5fe63c9
to
ed7595e
Compare
Clean rebase, no conflicts. |
Weird, there's no community type in the error screenshot. @alecmerdler fyi |
/retest |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: spadgett, vojtechszocs The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Follow-up to PR #1528.
From plugin perspective:
section
now links to all known sectionscomponentProps
now links to corresponding React component propsResourceClusterNavItem
extensionFrom Console perspective:
public/components/nav/index.jsx
into smaller parts that use TypeScript__REDUX_DEVTOOLS_EXTENSION_COMPOSE__
to globalWindow
declaration