diverta / front_nuxt_auth Goto Github PK

JavaScript 5.14% CSS 0.02% SCSS 21.76% Vue 70.31% TypeScript 2.76%

front_nuxt_auth's Introduction

Setup

Nodeバージョン

Nodeバージョンは .nvmrc 記載のバージョンに指定してください。
nvmを使用している場合は、nvm useで指定バージョンに切り替えができます。

ローカルサーバー起動

npm install
npm run dev

generate

npm run generate

Locally preview production build:

npm run preview

Nuxt 3 documentation

front_nuxt_auth's People

Contributors

Stargazers

Watchers

front_nuxt_auth's Issues

Design fixes

The nuxt3 version of the site has a lot of breaking design points due to incompaitibility across migration versions across vuetify, vue and nuxt
Reference deployment : https://dev-nuxt-auth.g.kuroco-front.app/

here are some examples :

@HisashiHasebe

Back button in article detail : https://diverta.gyazo.com/e27f0102b3b39c8f53fe5c6bc681fdd4

Fix inquiry page

Capture
https://diverta.gyazo.com/343afcec82bd65e3eb022c2f8a66d060

Error

{
    "errors": [
        {
            "code": "invalid",
            "message": "No valid results for anyOf {\n  0: Object expected, \"Radio1\" received at #->properties:ext_05->anyOf[0]\n  1: Enum failed, enum: [\"\",\"1\",\"2\",\"3\"], data: \"Radio1\" at #->properties:ext_05->anyOf[1]\n}",
            "field": "ext_05"
        }
    ],
    "x-rcms-request-id": "a4393ecd-48f6-4904-99ae-f22970581525"
}

Memo
This occurs only when tried with my own site key.

i18n maintenance

@TODO: Replace with the actual profile image URL

Provide github action's workflow onto Nuxt3 branch

Additional params for inquiry form

Currently inquiry form supports only the following data types by API fetch :

text
textarea
radio
select
checkbox
file

Should we extend this behaviour to

datepicker
matrix (single and multiple)

@HisashiHasebe san ?

Enclose template for need-login routes

For example /topics_list,
Those for pages login required should render only over client side, disable SSR for them.
Should use <ClientOnly> for them.

use localStorage

Keep sitekey to localStorage and restore it at initialization

There are 2 reasons why is:
keep loggedIn after refresh
let users use their own Kuroco backend

For the 2nd one,
The website is originally designed to be a template/demo for every incoming users.
If they try creating their own Kuroco backend, then users can change the sitekey to their own Kuroco’s sitekey and able to check that.
like this