-
Notifications
You must be signed in to change notification settings - Fork 44
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
Token launcher for home page #10447
base: master
Are you sure you want to change the base?
Token launcher for home page #10447
Conversation
@@ -317,6 +320,13 @@ const CommonDomainRoutes = ({ | |||
// GOVERNANCE END | |||
|
|||
// DISCUSSIONS | |||
<Route | |||
key="/:scope/community-home" |
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.
is this product decision that we will access the page with this URL like dydx/community-home
? For me it does not look good. for me home page should be just /dydx
or dydx/dashboard
or something. Please consult it with product
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.
probably we should also add it to custom domain routes
@@ -113,6 +118,31 @@ export const DiscussionSection = ({ | |||
localStorage[`${app.activeChainId()}-discussions-toggle-tree`], | |||
); | |||
const discussionsGroupData: SectionGroupAttrs[] = [ | |||
{ | |||
title: 'Community Home', |
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.
shouldn't we add it behind the feature flag?
modeOfManageCommunityStakeModal, | ||
} = useManageCommunityStakeModalStore(); | ||
|
||
const [selectedCommunityId] = useState<string>(); |
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 dont thing this needs to be in state. Or it will be modified in the upcoming prs?
} | ||
/> | ||
} | ||
// @ts-expect-error <StrictNullChecks/> |
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.
please avoid using StrictNullChecks everywhere
Link to Issue
Closes: #10266
Description of Changes
"How We Fixed It"
Test Plan
Deployment Plan
Other Considerations