When adding a ClientPolicy the Save button functionality is inconsistent · keycloak/keycloak#46623

(6 留言) (1 反應) (1 負責人)Java (34,398 star) (8,346 fork)batch import

area/admin/uiarea/oidchelp wantedkind/bugpriority/normalstatus/auto-bumpteam/core-clientsteam/core-shared

描述

Before reporting an issue

I have read and understood the above terms for submitting issues, and I understand that my issue may be closed without action if I do not follow them.

Area

admin/ui

Describe the bug

Currently when adding a Client Policy the Save button is enabled after a save, and can be disabled after a edit. Can also be enabled even if there is no change/additions to conditions or profiles, just by clicking the window.

Note that other behaviour - when renaming the policy and conditions/profiles disappearing after a save are handled in other tickets.

Version

latest

Regression

The issue is a regression

Expected behavior

Save button should be enabled when user either edits the policy name, adds/deletes a condition or adds/deletes a profile. If there is no change to any of these after a save, it shouldn't be enabled.

Actual behavior

As mentioned in the description

How to Reproduce?

As mentioned in the description

Anything else?

貢獻者指南

技術棧: reacttypescriptjavascript
領域: frontend
議題類型: bug
難度: 3
預計時間: 1-3 hours
活動狀態: blocked
清晰度: clear
前置要求: React state managementKeycloak admin UI basics
新手友善度: 40
研究方向: Look at the admin UI code for the Client Policy form, likely in the admin ui directory. Find the component controlling the Save button's disabled state. The issue relates to #45948, which may provide additional context. Since there is an assignee, check if any progress or linked branches exist in the comments.