3 commits

Author	SHA1	Message	Date
Panagiotis "Ivory" Vasilopoulos	103306f00c	UI: Disable internal wiki options when enabling external wiki ... Using "data-target", it is possible to set a value to a target element that can enable it or disable it. Using "data-context" lets us perform the opposite action on a different target. Before, only the #external_wiki_box target was used, which was enabled or disabled depending on whether the user has chosen to use the internal wiki or the external wiki. If the user chooses to use the internal wiki, they will disable the box that lets them enter a link pointing to an external wiki, and vice versa. Although it is not possible to use, say, boolean operations, we can introduce a target that is called #globally_writeable_checkbox that gets enabled when the #external_wiki_box box is disabled, and vice versa. This makes the box's behavior more consistent with the behavior in the "Issues" section. To keep things consistent with that section, a new property was assigned to the "globally_writeable_checkbox" that makes the box go a bit further in (`tw-pl-4`).	2024-04-29 20:29:00 +02:00
silverwind	c82bef515e	Migrate margin and padding helpers to tailwind (#30043) ... This will conclude the refactor of 1:1 class replacements to tailwind, except `gt-hidden`. Commands ran: ```bash perl -p -i -e 's#gt-(p|m)([lrtbxy])?-0#tw-$1$2-0#g' {web_src/js,templates,routers,services}/**/* perl -p -i -e 's#gt-(p|m)([lrtbxy])?-1#tw-$1$2-0.5#g' {web_src/js,templates,routers,services}/**/* perl -p -i -e 's#gt-(p|m)([lrtbxy])?-2#tw-$1$2-1#g' {web_src/js,templates,routers,services}/**/* perl -p -i -e 's#gt-(p|m)([lrtbxy])?-3#tw-$1$2-2#g' {web_src/js,templates,routers,services}/**/* perl -p -i -e 's#gt-(p|m)([lrtbxy])?-4#tw-$1$2-4#g' {web_src/js,templates,routers,services}/**/* perl -p -i -e 's#gt-(p|m)([lrtbxy])?-5#tw-$1$2-8#g' {web_src/js,templates,routers,services}/**/* ``` (cherry picked from commit 68ec9b48592fe88765bcc3a73093d43c98b315de) Conflicts: routers/web/repo/view.go templates/base/head_navbar.tmpl templates/repo/code/recently_pushed_new_branches.tmpl templates/repo/diff/box.tmpl templates/repo/diff/compare.tmpl templates/repo/diff/conversation.tmpl templates/repo/header.tmpl templates/repo/issue/filter_list.tmpl templates/repo/issue/view_content/conversation.tmpl templates/repo/issue/view_content/sidebar.tmpl templates/repo/settings/options.tmpl templates/repo/view_file.tmpl templates/shared/user/blocked_users.tmpl templates/status/500.tmpl web_src/js/components/DashboardRepoList.vue resolved by prefering Forgejo version and applying the commands to all files	2024-03-30 07:17:29 +01:00
Gergely Nagy	fa73375e13	Split out repository unit settings ... This splits out the repository unit settings (formerly "Advanced settings" under the repository settings page) into their own, separate page. The primary reason for this is that the settings page became long and complicated, with a structure that not always made sense. A secondary reason is that toggling units on and off should not necessarily be an "advanced" setting. We want to make doing that easier, and having the units on their own page helps with that. This is basically a refactor, there is no new functionality introduced, just an extra pair of routes for the new page, and the supporting code. Signed-off-by: Gergely Nagy <forgejo@gergo.csillger.hu>	2024-02-13 22:42:09 +01:00