Skip to content

Conversation

@arvid-e
Copy link
Contributor

@arvid-e arvid-e commented May 29, 2025

@arvid-e arvid-e requested review from miya and yuki-takei May 29, 2025 07:54
@changeset-bot
Copy link

changeset-bot bot commented May 29, 2025

⚠️ No Changeset found

Latest commit: 73d89b4

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Comment on lines +29 to +30
"always_hidden": "表示しない",
"always_displayed": "表示する",
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

"displayed" と "hidden" の値と同じものなので、それらを使うようにして良さそう

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

フィードバック: hideRestrictedByOwner のデフォルト値に関する注意

  • 現在の実装では、DB から得られる generalSetting.hideRestrictedByOwnerundefined の場合、currentOwnerRestrictionDisplayMode'Displayed' となります。
  • サーバーから hideRestrictedByOwner が返却されないケース(値がない場合)、デフォルトで「閲覧制限が表示される」挙動になっており、意図しない情報公開(セキュリティのデグレ)リスクがあります。

推奨対応

  • hideRestrictedByOwnerundefined の場合は、保守的に 'Hidden' 扱いとしてください。
  • 例:
    currentOwnerRestrictionDisplayMode: generalSetting.hideRestrictedByOwner === undefined
      ? 'Hidden'
      : (generalSetting.hideRestrictedByOwner ? 'Hidden' : 'Displayed'),
  • この挙動・仕様をコードコメントでも明記してください

@arvid-e arvid-e requested a review from yuki-takei June 4, 2025 04:20
mergify bot added a commit that referenced this pull request Jun 4, 2025
@mergify
Copy link
Contributor

mergify bot commented Jun 4, 2025

This pull request has been removed from the queue for the following reason: checks failed.

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.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@yuki-takei
Copy link
Contributor

@mergify requeue

@mergify
Copy link
Contributor

mergify bot commented Jun 4, 2025

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

mergify bot added a commit that referenced this pull request Jun 4, 2025
@mergify
Copy link
Contributor

mergify bot commented Jun 4, 2025

This pull request has been removed from the queue for the following reason: checks failed.

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.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

@yuki-takei
Copy link
Contributor

@mergify requeue

@mergify
Copy link
Contributor

mergify bot commented Jun 4, 2025

requeue

✅ The queue state of this pull request has been cleaned. It can be re-embarked automatically

mergify bot added a commit that referenced this pull request Jun 4, 2025
mergify bot added a commit that referenced this pull request Jun 4, 2025
mergify bot added a commit that referenced this pull request Jun 4, 2025
@mergify
Copy link
Contributor

mergify bot commented Jun 4, 2025

This pull request has been removed from the queue for the following reason: checks failed.

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.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

mergify bot added a commit that referenced this pull request Jun 5, 2025
@mergify
Copy link
Contributor

mergify bot commented Jun 5, 2025

This pull request has been removed from the queue for the following reason: checks failed.

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.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

mergify bot added a commit that referenced this pull request Jun 5, 2025
@mergify
Copy link
Contributor

mergify bot commented Jun 5, 2025

This pull request has been removed from the queue for the following reason: checks failed.

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.
If you update this pull request, to fix the CI, it will automatically be requeued once the queue conditions match again.
If you think this was a flaky issue instead, you can requeue the pull request, without updating it, by posting a @mergifyio requeue comment.

mergify bot added a commit that referenced this pull request Jun 6, 2025
@mergify mergify bot merged commit 0d57a9d into master Jun 6, 2025
22 checks passed
@mergify mergify bot deleted the imprv/153742-security-settings-pagelist-content-improvement branch June 6, 2025 03:21
@github-actions github-actions bot mentioned this pull request Jun 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants