-
Notifications
You must be signed in to change notification settings - Fork 236
imprv: Security settings search results redesign #9992
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
imprv: Security settings search results redesign #9992
Conversation
|
| "always_hidden": "表示しない", | ||
| "always_displayed": "表示する", |
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.
"displayed" と "hidden" の値と同じものなので、それらを使うようにして良さそう
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.
フィードバック: hideRestrictedByOwner のデフォルト値に関する注意
- 現在の実装では、DB から得られる
generalSetting.hideRestrictedByOwnerがundefinedの場合、currentOwnerRestrictionDisplayModeが'Displayed'となります。 - サーバーから
hideRestrictedByOwnerが返却されないケース(値がない場合)、デフォルトで「閲覧制限が表示される」挙動になっており、意図しない情報公開(セキュリティのデグレ)リスクがあります。
推奨対応
hideRestrictedByOwnerがundefinedの場合は、保守的に'Hidden'扱いとしてください。- 例:
currentOwnerRestrictionDisplayMode: generalSetting.hideRestrictedByOwner === undefined ? 'Hidden' : (generalSetting.hideRestrictedByOwner ? 'Hidden' : 'Displayed'),
- この挙動・仕様をコードコメントでも明記してください
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks:
You can check the last failing draft PR here: #10014. You may have to fix your CI before adding the pull request to the queue again. |
|
@mergify requeue |
✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically |
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks:
You can check the last failing draft PR here: #10015. You may have to fix your CI before adding the pull request to the queue again. |
|
@mergify requeue |
✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically |
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks:
You can check the last failing draft PR here: #10018. You may have to fix your CI before adding the pull request to the queue again. |
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks:
You can check the last failing draft PR here: #10026. You may have to fix your CI before adding the pull request to the queue again. |
|
This pull request has been removed from the queue for the following reason: The merge conditions cannot be satisfied due to failing checks:
You can check the last failing draft PR here: #10028. You may have to fix your CI before adding the pull request to the queue again. |
TASK
https://redmine.weseek.co.jp/issues/153742
┗https://redmine.weseek.co.jp/issues/153037