discourse/app
Krzysztof Kotlarek 1f1709d249
FIX: use a custom prefix for custom flags (#28839)
Currently, when the custom flag has the same name as the system flag (which is disabled) then it is not displayed. To fix the problem, `custom_` prefix as `name_key` is used to distinguish between the system and the custom flag.

I considered writing a migration to fix existing custom flags name key. However, at the end of migration I would need to run rails code to reset cache `Flag.reset_flag_settings!`. I decided to skip that step as it is a very edge case. If someone has the same flag name as the system flag, then all they have to do is edit the flag and click save.

In addition, I made 2 small fixes:
- edit flag title was missing translation;
- flag form UI was not showing that description is the required field.
2024-09-11 15:30:20 +10:00
..
assets FIX: use a custom prefix for custom flags (#28839) 2024-09-11 15:30:20 +10:00
controllers FEATURE: Switch to new methods of pageview measurement and reporting (#28729) 2024-09-10 09:51:49 +10:00
helpers DEV: Drop WithServiceHelper 2024-09-05 09:58:20 +02:00
jobs DEV: Remove old problem check system - Part 1 (#28772) 2024-09-06 17:00:25 +08:00
mailers UX: Use a dropdown for SSL mode for group SMTP (#27932) 2024-07-18 10:33:14 +10:00
models FIX: use a custom prefix for custom flags (#28839) 2024-09-11 15:30:20 +10:00
serializers FEATURE: Support designating multiple groups as mods on category (#28655) 2024-09-04 04:38:46 +03:00
services FEATURE: Log tag group changes in staff action log (#28787) 2024-09-09 10:50:48 +08:00
views UX: Upgrade to fontawesome 6.6.0 (#28778) 2024-09-09 14:40:56 +01:00