wxiaoguang
48d4580dd5
Clarify permission "HasAccess" behavior ( #30585 )
...
Follow #30495
"HasAccess" behavior wasn't clear, to make it clear:
* Use a new name `HasAnyUnitAccess`, it will be easier to review related
code and permission problems.
* Separate everyone access mode to a separate field, then all calls to
HasAccess are reverted to old behavior before #30495 .
* Add new tests.
---------
Co-authored-by: Giteabot <teabot@gitea.io>
2024-04-20 03:15:04 +00:00
..
2024-02-27 08:12:22 +01:00
2024-04-13 08:38:44 +00:00
2024-04-07 19:17:06 +08:00
2023-04-22 17:56:27 -04:00
2024-03-22 13:53:52 +01:00
2023-02-28 16:17:51 -06:00
2023-05-13 20:59:11 +02:00
2024-04-13 08:38:44 +00:00
2023-12-19 09:29:05 +00:00
2024-02-02 19:11:39 -05:00
2024-03-04 08:16:03 +00:00
2024-03-04 08:16:03 +00:00
2024-02-27 08:12:22 +01:00
2024-04-13 08:38:44 +00:00
2024-04-13 08:38:44 +00:00
2024-02-14 18:19:57 +00:00
2024-03-08 15:30:10 +08:00
2023-10-19 13:16:11 +00:00
2024-04-20 03:15:04 +00:00
2022-12-27 15:21:14 -06:00
2024-03-04 08:16:03 +00:00
2024-02-28 14:40:36 +01:00
2024-03-08 15:30:10 +08:00
2024-01-27 21:09:51 +01:00
2024-02-28 14:40:36 +01:00
2023-12-07 15:27:36 +08:00
2024-02-24 06:55:19 +00:00
2023-09-28 01:38:53 +00:00
2024-03-08 15:30:10 +08:00
2024-03-08 10:21:24 +00:00
2022-12-03 10:48:26 +08:00
2023-10-18 15:03:10 +00:00
2023-02-28 16:17:51 -06:00
2023-02-28 16:17:51 -06:00
2024-01-31 14:55:12 +00:00
2024-02-28 14:40:36 +01:00
2024-04-20 03:15:04 +00:00
2024-04-20 03:15:04 +00:00