-
Notifications
You must be signed in to change notification settings - Fork 45
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: group new topic page #320
Conversation
Textarea should have both left and right padding. Textarea handle should fit into container rounded corner.
Preview DeploymentStorybook https://pr-320-storybook--bangumi-next.netlify.app |
Codecov ReportBase: 88.81% // Head: 88.70% // Decreases project coverage by
Additional details and impacted files@@ Coverage Diff @@
## master #320 +/- ##
==========================================
- Coverage 88.81% 88.70% -0.12%
==========================================
Files 86 88 +2
Lines 4874 5019 +145
Branches 517 529 +12
==========================================
+ Hits 4329 4452 +123
- Misses 545 567 +22
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report at Codecov. |
So that react-hook-form can focus the field when there's an error.
To ease the use with react-hook-form
如果觉得合并进来不应该是一个commit的话直接分成几个PR比较好吧。 登录的问题等着跟sai老板商量一下sso... |
主要这些都是跟这个 PR 关联的一些前置重构和修复,如果拆的话不就得多出三四个额外的 PR? 不明白一个 PR 产生多个 commit 有什么问题…… |
一个 PR 尽量只干一件事情,更小的 PR 会更好 review 一点 |
我的习惯是维护一个整洁的 commit 历史,然后就可以按 commit review。 那我看看再拆两个 PR 出来吧…… 按我的理解每个 commit 都是做一件事,如果每个 PR 也只做一件事的话就得有 6 个 PR |
fix: styles refactor: clean up styles
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.
没检查用户是否登录?
维基编辑页也没检查吧,等于这里也是交给后端做了,前端检查后面跟权限一起做吧? |
那分成不同的pr后面再加上吧。 顺便做个某些路由下未登录时转跳登录页面,登录成功后再转跳回来的功能。 |
你提醒我了,这个之前打算做的b38 |
功能看起来ok,代码等其他人review了 |
还需要根据设计稿更新一下小组信息这个组件 🤔 |
左右宽度跟设计稿不太一样,是要放在另外的PR? |
是,我上面说了,做的过程中设计稿改了,但是小组的左右栏布局和维基编辑页是一样的,设计稿里貌似还没改完 |
可以
|
@cokemine 当初这里是为啥要 9999,现在会导致覆盖掉了Header,Header是5000 |
另开 Issue 或 PR 讨论吧,这块坑挺多的,组件那里在写小组讨论页的时候把宽度写死了还没改 |
确实,感觉还涉及到 EditorForm 和 Form 的问题 |
应该是当时被其他的给盖住了。就直接设了9999,调成5000以内应该不会有啥问题 |
主要是为了契合原站逻辑,如果直接固定宽度的话这个应该还可以简化一些,为了可以自由调整宽度当时这个编辑框的写法也是挺奇怪的,也没有考虑到上面可能还一个框要跟着动( |
额。。merge 了,还想让 @Ayase-252 看下的(尴尬 |
close #235
http://localhost:5173/group/sandbox/new_topic
https://pr-320-sites--bangumi-next.netlify.app/group/sandbox/new_topic
/group/[name]
里的页面移到了/group/[name]/index
目录里