-
Notifications
You must be signed in to change notification settings - Fork 1
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: vue starter app #21
base: main
Are you sure you want to change the base?
Conversation
There is currently a dependency issue (security vulnerability) with |
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.
First round of review - I have a few files left that I will continue with tomorrow
<AppLink :to="getLocalizedPath('about/about1')">{{ t('aboutPage.about1.heading') }}</AppLink> | ||
</section> | ||
<section> | ||
<AppLink :to="getLocalizedPath('about/about2')">{{ t('aboutPage.about2.heading') }}</AppLink> |
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.
Do you think it might be beneficial to rename these pages to avoid confusion? Initially, I found it a little unclear having 3 pages with almost identical names.
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.
Yes! Any recommendations? I'm feeling less creative so put these in as a placeholder 👯
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.
topic-one and topic-two?
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.
Just a couple comments/questions.
Do we plan to replace the lorem ipsum in the app content with other content?
@gcdsValid="handleValid" | ||
@submit.prevent="handleSubmit" | ||
> | ||
<Input |
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.
Could we add an error summary into this form since it is a bigger form? You could then switch each form component to validate on submit.
<gcds-header :lang-href="getOtherLangPath" skip-to-href="#main"> | ||
<gcds-search slot="search"></gcds-search> | ||
<div slot="toggle"> | ||
<AppLink :to="getOtherLangPath">{{ t('langToggle') }}</AppLink> |
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.
Are you able to use the same logic you used for the gcds-nav-link
on the gcds-lang-toggle
? That way the language toggle will have the proper responsive styling.
Summary | Résumé
Adds a starter app for usage in Vue 3.
This starter app contains the following: