Closed aliemir closed 3 months ago
Latest commit: 7f9ca52df6b75fee63cb1c8a483579f4fd0553df
The changes in this PR will be included in the next version bump.
Not sure what this means? Click here to learn what changesets are.
Click here if you're a maintainer who wants to add another changeset to this PR
0 | 82 | 23 | 0 | 0 |
Details:
Merge 7f9ca52df6b75fee63cb1c8a483579f4fd0553df into 2c3f96e2de0dba70ea84f5e48cd2... | |||
Project: refine | Commit: d24455f032 ℹ️ |
||
Status: Passed | Duration: 15:53 💡 | ||
Started: Jul 28, 2024 7:20 AM | Ended: Jul 28, 2024 7:36 AM |
0 | 381 | 37 | 0 | 0 |
Details:
fix(docs): correct import path and notification provider usage (#6195) | |||
Project: refine | Commit: c61c4143dd |
||
Status: Passed | Duration: 18:39 💡 | ||
Started: Jul 28, 2024 6:11 AM | Ended: Jul 28, 2024 6:30 AM |
PR Checklist
Please check if your PR fulfills the following requirements:
Bugs / Features
Changes
fix(auth-page): fix wrong translation keys in
type="register"
andtype="forgotPassword"
In
type="forgotPassword"
:"pages.register.buttons.haveAccount"
is replaced with"pages.forgotPassword.buttons.haveAccount"
"pages.login.signin"
is replaced with"pages.forgotPassword.signin"
In
type="register"
:"pages.login.divider"
is replaced with"pages.register.divider"
"pages.login.buttons.haveAccount"
is replaced with"pages.register.buttons.haveAccount"
"pages.login.signin"
is replaced with"pages.register.signin"
Wrong keys are kept as fallbacks in case the new keys are not found in the translation file. If you are using those keys in your project, make sure to update them accordingly. Fallback keys will be removed in future releases.
Fixes #5816
fix(auth-page): fix wrong translation key in
type="register"
Previously, sign in link in Register page was using wrong translation key "pages.register.buttons.noAccount". Now it is replaced with "pages.register.buttons.haveAccount".