Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Incorrect field rendering in DAG Params #45574

Closed

Conversation

rawwar
Copy link
Collaborator

@rawwar rawwar commented Jan 11, 2025

closes #45290

@boring-cyborg boring-cyborg bot added area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues labels Jan 11, 2025
@rawwar
Copy link
Collaborator Author

rawwar commented Jan 11, 2025

Even after removing the condition, validations are happening.

@rawwar rawwar requested a review from jscheffl January 11, 2025 09:14
@rawwar rawwar marked this pull request as ready for review January 11, 2025 09:15
@rawwar rawwar added the legacy ui Whether legacy UI change should be allowed in PR label Jan 11, 2025
Copy link
Contributor

@jscheffl jscheffl left a comment

Choose a reason for hiding this comment

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

Handling of non string types array was added as a feature some time ago.

I don't see this as a "bug" and forcing users to enter a list of strings in JSON is something that I would very mus dis-like.

New features in this area and improvements for more options can be added in 3.x, but in 2.10-line we should keep it like it is.

@rawwar rawwar closed this Jan 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:UI Related to UI/UX. For Frontend Developers. area:webserver Webserver related Issues legacy ui Whether legacy UI change should be allowed in PR
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants