vitorsantos-commits commented on issue #6617: URL: https://github.com/apache/hop/issues/6617#issuecomment-3935553746
<img width="1061" height="345" alt="Image" src="https://github.com/user-attachments/assets/36fd7ee1-35d4-4a23-99d2-be7434bad6a6"; /> I understand the Environment-driven approach, Matt, but I still believe having the option to set a color directly on the Database Connection is vital for user experience. In many real-world scenarios, we have specific databases that are always production (like a legacy ERP or a sensitive DW) regardless of the Hop Environment we are using. If the color is tied only to the Environment, a user might still get confused if they have multiple connections open from different sources. My proposal is to have a 'Display Color' field in the Connection Metadata. This would allow: Visual Consistency: The user knows that 'Red' always means that specific sensitive database. Immediate Identification: Even if I'm in a 'Dev' environment, if I'm pointing to a 'Production' database for a read-only task, I want to see it in red to be extremely careful. DBeaver does this very well because it treats the connection's visual identity as a safety layer. Could we consider this as an optional field in the Connection Metadata?" -- 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]
