-
Notifications
You must be signed in to change notification settings - Fork 0
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
Feature/plan/dmp overview static frontend #356
base: development
Are you sure you want to change the base?
Feature/plan/dmp overview static frontend #356
Conversation
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 wasn't sure how translations would work with this page, so kind of left its pretty minimal. As guess a lot of the values will come from the database etc?
@@ -277,6 +300,149 @@ const PlanOverviewPage: React.FC = () => { | |||
</div> | |||
</SidebarPanel> | |||
</LayoutWithPanel> | |||
|
|||
|
|||
<Modal isDismissable isOpen={isPublishModalOpen}> |
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.
Modal for publish flow. I wonder whether these modals should be componentized?
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 agree that eventually we should make all of these into shared components.
font-weight: 400; | ||
} | ||
} | ||
|
||
.react-aria-Radio { | ||
display: flex; | ||
align-items: center; | ||
align-items: flex-start; |
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.
Potentially semi breaking change - but the radio button when we had helper text it put the "radio" in an awkward location, so I placed at the top again.
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 think it'll be fine. It didn't break other pages with radio buttons as far as I can tell
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.
Thanks Fraser. I just had a few comments. Some of these changes do need to be made to address linting issues.
|
||
/* File format selection */ | ||
.formatChoices { | ||
display: flex; |
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.
For any space styles, like gap
or margin
, are we supposed to be using the shared --space-#
styles?
|
||
|
||
expect.extend(toHaveNoViolations); | ||
jest.mock('next-intl', () => ({ |
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.
L9 - Just an FYI. If you merge in the latest from development, you will get the mock for useTranslations for free, since it was added to the 1jest.setup.ts1 file
|
||
|
||
|
||
<LayoutWithPanel> |
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.
L99: I think we can use LayoutContainer
here instead of LayoutWithPanel
since there is no sidebar on this page.
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.
Good spot - will fix
</Form> | ||
</div> | ||
</ContentContainer> | ||
<SidebarPanel/> |
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.
L192: Don't think the SidebarPanel
is needed here?
<div className={styles.formGroup}> | ||
<h3 className={styles.sectionLabel}>What should this person be | ||
able to do?</h3> | ||
<CheckboxGroup |
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.
L133: Just an FYI - We have a shared CheckboxGroupComponent now at components/Form/CheckboxGroup
. No worries though. We can update this as we're working on hooking up the page.
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.
Yeah sorry, I will double check these iņ the future
@@ -277,6 +300,149 @@ const PlanOverviewPage: React.FC = () => { | |||
</div> | |||
</SidebarPanel> | |||
</LayoutWithPanel> | |||
|
|||
|
|||
<Modal isDismissable isOpen={isPublishModalOpen}> |
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 agree that eventually we should make all of these into shared components.
font-weight: 400; | ||
} | ||
} | ||
|
||
.react-aria-Radio { | ||
display: flex; | ||
align-items: center; | ||
align-items: flex-start; |
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 think it'll be fine. It didn't break other pages with radio buttons as far as I can tell
} | ||
|
||
// Form submission logic | ||
console.log('Inviting user:', {email, accessType}); |
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.
L47: Did you mean to keep the console.log here?
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 will remove
|
||
<div className={styles.formHelp}> | ||
<p> | ||
When you click <strong>Grant access</strong> we'll send an |
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.
L176, 181, 182 - I think we need to replace all apostrophes in the page with an entity like ‘
, otherwise the build will pick up on the linting error.
@@ -14,6 +23,15 @@ import { | |||
|
|||
const PlanOverviewPage: React.FC = () => { | |||
const t = useTranslations('PlanOverview'); | |||
let [isPublishModalOpen, setPublishModalOpen] = useState(false); |
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.
L26, 27, 28 - The 'let' in all three lines can be changed to a 'const' since these do not change.
Description
Pulling in the remaining parts of DMP plans.
I need to add translations to some of the pages these were built previously just hadn't merged them in properly; Will finish that off tomorrow.
Type of change
Checklist: