chakilamsuryat opened a new pull request, #32012:
URL: https://github.com/apache/superset/pull/32012

   <!---
   Please write the PR title following the conventions at 
https://www.conventionalcommits.org/en/v1.0.0/
   Example:
   fix(dashboard): load charts correctly
   -->
   
   ### SUMMARY
   <!--- Describe the change below, including rationale and design decisions -->
   No input validations there on UI
   
   ### BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
   <!--- Skip this if not applicable -->
   Before: 
   <img width="1790" alt="before-dashboard" 
src="https://github.com/user-attachments/assets/e2931382-9bd3-4f99-9b18-07ad0e575c7d";
 />
   After:
   <img width="1783" alt="Screenshot 2025-01-28 at 3 56 48 PM" 
src="https://github.com/user-attachments/assets/773de306-152b-427e-aea0-573141d878c6";
 />
   We will restricting the user for input validation and will thrown error as 
shown above.
   
   ### TESTING INSTRUCTIONS
   <!--- Required! What steps can be taken to manually verify the changes? -->
   Can test charts, dashboards, annotations, annotation_layers, 
row_level_security, user info editing views on the UI for input validation 
given for names and descriptions.
   
   ### ADDITIONAL INFORMATION
   <!--- Check any relevant boxes with "x" -->
   <!--- HINT: Include "Fixes #nnn" if you are fixing an existing issue -->
   There is no input validation present for Dashboard, Chart, Annotation 
Layers, row-level-security, and for user info details.
   This is as part of security fixes for vulnerabilities raised as able to 
input scripts also currently in the fields of name and descriptions of various 
views.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to