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
In my deno projects, I often use Rust via ffi and I was wondering if we could unify the naming conventions.
It may have been proposed already (Discord?), yet I didn't find an issue for the following proposal:
Similar to https://rust-lang.github.io/api-guidelines/naming.html a lint rule that enforces UpperCamelCase for types, interfaces and classes and snake_case for functions, methods and variables plus SCREAMING_SNAKE_CASE for constants (if enforcible) would be great.
pros: uniform naming across Rust and TypeScript
cons: JS legacy naming convention is camelCase
The text was updated successfully, but these errors were encountered:
In my deno projects, I often use Rust via ffi and I was wondering if we could unify the naming conventions.
It may have been proposed already (Discord?), yet I didn't find an issue for the following proposal:
Similar to https://rust-lang.github.io/api-guidelines/naming.html a lint rule that enforces
UpperCamelCase
for types, interfaces and classes andsnake_case
for functions, methods and variables plusSCREAMING_SNAKE_CASE
for constants (if enforcible) would be great.pros: uniform naming across Rust and TypeScript
cons: JS legacy naming convention is
camelCase
The text was updated successfully, but these errors were encountered: