Vam-tech-star commented on issue #28252: URL: https://github.com/apache/superset/issues/28252#issuecomment-2580251263
Hi Ajay-Satish-01 Thank you for your question and for your interest in contributing to Apache Superset. The current behavior where the schema field becomes immutable after being populated might be intentional to prevent accidental modifications to critical database configurations. However, this can be inconvenient in scenarios where updates to the schema are necessary. To address this, we can consider the following approach: 1.)Make the Schema Editable: This allow users to edit the schema field after it has been populated to provide flexibility for making necessary updates without resetting the entire configuration. 2.)Add a Confirmation Mechanism: Implement a confirmation dialog that prompts users to confirm changes to the schema. This can help prevent accidental modifications while still allowing for updates when needed. 3.)Version Control for Configurations: Introduce a version control mechanism for database configurations. This way, any changes to the schema can be tracked, and users can revert to previous configurations if necessary. 4.)User Permissions: Ensure that only users with the appropriate permissions can edit the schema field. This can help maintain the integrity of the database configurations. Next Steps: Discuss with the maintainers or the community to get their input on whether making the schema editable aligns with the project's design principles. Implement the changes based on the feedback received. Thoroughly test the implementation to ensure it works as expected and does not introduce any new issues. By making the schema field editable with the appropriate safeguards, we can provide a more flexible and user-friendly experience while maintaining the integrity of the database configurations. Your feedback on this approach would be greatly appreciated. Best regards, Vam-tech-star -- 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]
