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
The existing Pull requests are slightly different from the existing code in the core repository in terms of function names and test names. Is it necessary to develop a unified standard to manage?
The text was updated successfully, but these errors were encountered:
I would +1 to an overall style guideline in addition to the current CONTRIBUTING tutorial. However, I also understand that things are still moving fast at this early stage and perhaps a loose standard is preferred.
I would +1 to an overall style guideline in addition to the current CONTRIBUTING tutorial. However, I also understand that things are still moving fast at this early stage and perhaps a loose standard is preferred.
Maybe you're right, we may have to wait a while to unify these things. This way we can maximize our productivity.
If it is a simple restriction identifier style (such as snake_case or CamelCase), it should not have any impact. The current overall code style is snake_case.
The existing Pull requests are slightly different from the existing code in the core repository in terms of function names and test names. Is it necessary to develop a unified standard to manage?
The text was updated successfully, but these errors were encountered: