You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
First and foremost, I want to say a huge thank you 🙏 for your work on mirromutth/mysql-action@v1.1. It has been an incredibly helpful tool that has greatly enhanced our workflow.
In using this action, I've noticed that the current configuration employs spaces in its property names, such as host port, container port, character set server, collation server, mysql version, mysql database, mysql root password, mysql user, mysql password and so on.
This is a bit unusual 🧐 when compared to most naming conventions in programming languages or configuration schemas and could potentially lead to confusion or errors. Additionally, we've found this to be a blocker 🚧 when trying to use sbt-github-actions as it validates the YML based on these naming conventions.
Hence, I'd like to propose 📝 a small but significant improvement. Let's standardize the naming convention to something more common, like CamelCase (hostPort, containerPort, characterSetServer, collationServer, mysqlVersion, etc.) or snake_case (host_port, container_port, character_set_server, collation_server, mysql_version, etc.).
Switching to a more standardized configuration property naming could pave the way for a more intuitive and consistent developer experience 🚀.
Thank you 🙏 for your effort on this action, and I'm convinced these changes would go a long way in enhancing its usability and the overall developer experience.
Thank you for considering this proposal 📜. I'm eagerly looking forward to your thoughts on this.
Best regards,
Tushar
The text was updated successfully, but these errors were encountered:
Hello 👋,
First and foremost, I want to say a huge thank you 🙏 for your work on
mirromutth/mysql-action@v1.1
. It has been an incredibly helpful tool that has greatly enhanced our workflow.In using this action, I've noticed that the current configuration employs spaces in its property names, such as
host port
,container port
,character set server
,collation server
,mysql version
,mysql database
,mysql root password
,mysql user
,mysql password
and so on.This is a bit unusual 🧐 when compared to most naming conventions in programming languages or configuration schemas and could potentially lead to confusion or errors. Additionally, we've found this to be a blocker 🚧 when trying to use
sbt-github-actions
as it validates the YML based on these naming conventions.Hence, I'd like to propose 📝 a small but significant improvement. Let's standardize the naming convention to something more common, like CamelCase (
hostPort
,containerPort
,characterSetServer
,collationServer
,mysqlVersion
, etc.) or snake_case (host_port
,container_port
,character_set_server
,collation_server
,mysql_version
, etc.).Switching to a more standardized configuration property naming could pave the way for a more intuitive and consistent developer experience 🚀.
Thank you 🙏 for your effort on this action, and I'm convinced these changes would go a long way in enhancing its usability and the overall developer experience.
Thank you for considering this proposal 📜. I'm eagerly looking forward to your thoughts on this.
Best regards,
Tushar
The text was updated successfully, but these errors were encountered: