-
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
refactor: Next.js13.4 App Routerへの移行 #21
Merged
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
kyonenya
changed the title
chore: pagesディレクトリを退避してapp directoryを掘る
refactor: Next.js13.4 App Routerへの移行
Jun 19, 2023
完コピで草
|
やっつけローディングページ・ボタンスタイル上書き・バリデーションが適当
kyonenya
commented
Jul 3, 2023
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.
- ログインせず見る、ボタン
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
kyonenya
commented
Jul 3, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
参考
register
で事を済ませたいよね@media print
isDisabled
をカスタムデータ属性でスタイリングuseSearchParams
良さげじゃんと思ったけどかなりしんどいことやってる。router.push
も文字列しか受け取らない仕様になってるしDialog API
に勝るComponentProps
twMerge
を極力使わないServer Actions のエラーハンドリング
結論:無理。Server Component には useState がないが、データフェッチ後のエラー表示には state 相当のものが必要なので、無理です
useFormStatus
はpending
だけのようだがuseFormStatus
にerror
も含まれてると言ってる。本当ならそれで済む話useState
なしでエラーハンドリングするって縛りが困難なのか?formAction
とか<form action={/* ... */}>
みたいな記述がなくただonClick
にサーバーサイド関数ハンドラを渡してるぞSupabase Auth