-
-
Notifications
You must be signed in to change notification settings - Fork 9.7k
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: add verification function to the notification settings for the mailbox #5464
feat: add verification function to the notification settings for the mailbox #5464
Conversation
hi @longjuan ,有时间可以尝试一下基于此 PR 为 S3 插件的配置表单添加一个验证。 |
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #5464 +/- ##
============================================
- Coverage 56.91% 56.49% -0.43%
- Complexity 3319 3320 +1
============================================
Files 587 595 +8
Lines 18968 19249 +281
Branches 1401 1357 -44
============================================
+ Hits 10795 10874 +79
- Misses 7594 7813 +219
+ Partials 579 562 -17 ☔ View full report in Codecov by Sentry. |
hi @LIlGG,在合并此 PR 前,建议同时提交对应文档的修改 PR。 |
hi, @guqing ,目前还缺少验证邮箱是否联通的后端接口,有时间的话帮忙补充一下。 |
22e0c63
to
0556d41
Compare
已补充 |
longjuan/halo-plugin-s3os@e9bba38 |
application/src/main/resources/extensions/role-template-notification.yaml
Outdated
Show resolved
Hide resolved
4e8775a
to
d154ba6
Compare
a2949f0
to
0044d34
Compare
已进行修复,你可以强制拉取一下最新的代码再进行测试。 |
c936f19
to
3426082
Compare
有个建议: |
s3 1.8+halo 2.13配置升级到s3 1.8+本pr:无问题 但s3测试分支+本pr 新建策略并编辑会出现名称闪现后消失的问题(旧版本保存的配置没问题) 2024-03-11_20-39-25.mp4 |
目前验证按钮是无状态的。另外对于已经保存的内容,再次打开是无法确定是否经过了验证。 不过可以考虑单轮配置阶段增加图标,例如在验证完成之后,加一个验证通过的图标。在修改配置之后,恢复初始状态。 |
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.
IMO,支持验证表单和邮箱验证测试应该是两个功能,如果能够拆分一下提交会不会更好呢?
我认为虽然是可以进行拆分,但此 PR 主要还是用于添加邮箱验证测试这个业务功能,而验证表单是为了满足此业务而产生的组件。例如在写文章列表的同时抽象出一个用于展示列表的公共组件,本质上是同一件事情。 |
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.
/lgtm
Quality Gate passedIssues Measures |
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.
/lgtm
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.
/lgtm
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: ruibaby The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
为 FormKit Schema 文档添加 verifyForm 的内容。相关改动查看 halo-dev/halo#5464 /kind documentation ```release-note None ```
What type of PR is this?
/kind feature
/area ui
/area core
/milestone 2.14.x
What this PR does / why we need it:
为邮件的
通知设置
添加验证的功能。同时为 formkit 增加了一个新的组件 (verificationForm),用于支持验证,它的定义方式如下:
verificationForm 支持
action
属性,当前端数据验证通过时,会将其下所包含的子节点数据发送至 action 所代表的接口上。按上述示例,则验证数据会提交至
http://localhost:8090/verify/user
进行验证。验证的数据为{name: xxx, password: xxx}
需要注意的是,verificationForm 只用于包装需要验证的数据,不会破坏原始数据的格式。因此上述数据在提交保存后仍旧为
{name: xxx, password: xxx}
而不会变成{verificationForm1: {name: xxx, password: xxx}}
How to test it?
通知设置
新增的验证按钮是否可以正常验证邮箱。Which issue(s) this PR fixes:
Fixes #4714
Does this PR introduce a user-facing change?