Skip to content
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

Open
wants to merge 21 commits into
base: main
Choose a base branch
from
Open

feat: vue starter app #21

wants to merge 21 commits into from

Conversation

daine
Copy link
Collaborator

@daine daine commented Sep 4, 2024

Summary | Résumé

Adds a starter app for usage in Vue 3.

This starter app contains the following:

  • Regular JS (I'm hoping we can produce a typescript equivalent in the near future)
  • Vue Router
  • Pinia for state management
  • VI tests for unit tests
  • Playwright for E2E tests
  • ESLint configuration
  • Prettier configuration

@daine
Copy link
Collaborator Author

daine commented Sep 11, 2024

There is currently a dependency issue (security vulnerability) with send version 0.18.0 which I've traced to the serve-static package. Here is a PR, hoping it gets merged and published soon.

Copy link
Contributor

@melaniebmn melaniebmn left a 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

starter-apps/vue/vue-template/index.html Outdated Show resolved Hide resolved
starter-apps/vue/vue-template/package.json Outdated Show resolved Hide resolved
starter-apps/vue/vue-template/src/App.vue Outdated Show resolved Hide resolved
starter-apps/vue/vue-template/src/App.vue Outdated Show resolved Hide resolved
starter-apps/vue/vue-template/src/views/About/About1.vue Outdated Show resolved Hide resolved
<AppLink :to="getLocalizedPath('about/about1')">{{ t('aboutPage.about1.heading') }}</AppLink>
</section>
<section>
<AppLink :to="getLocalizedPath('about/about2')">{{ t('aboutPage.about2.heading') }}</AppLink>
Copy link
Contributor

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.

Copy link
Collaborator Author

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 👯

Copy link
Contributor

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?

Copy link
Contributor

@ethanWallace ethanWallace left a 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
Copy link
Contributor

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>
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants