-
Notifications
You must be signed in to change notification settings - Fork 5
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add an error to go-runtime/compile
when local Go identifier casing differs from FTL
#1482
Comments
@alecthomas the team had some questions around this in standup and we wanted to make sure we understand the issue we're trying to solve here. Do you mind clarifying what behavior you want to error on? I was guessing it was the case where you write Thanks! |
That's exactly right. In the owning module |
Currently it's possible for a symbol to have two different casings within an FTL system - the native casing and the normalised FTL casing. We normalise casing across all languages to
lowerCamelCase
for fields and values, andUpperCamelCase
for all types.For example, if you have the following Go type:
This will be case-transformed to:
We should raise an error in this case.
The text was updated successfully, but these errors were encountered: