-
Notifications
You must be signed in to change notification settings - Fork 7
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
fix: ensure topic name matches idiomatic variable name #1958
Conversation
|
go-runtime/compile/schema.go
Outdated
if t, ok := varDecl.Specs[0].(*ast.ValueSpec); ok { | ||
varName := t.Names[0].Name | ||
if expVarName := strcase.ToUpperCamel(name); varName != expVarName { | ||
pctx.errors.add(errorf(node, "unexpected topic variable name %q, did you mean %q?", varName, expVarName)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
nice
b69adf0
to
8871202
Compare
@safeer is this one ready to merge or do you have more changes coming? |
@wesbillman this is a breaking change that requires clients to update their topic varnames |
c8c38ae
to
ae7f5c5
Compare
Introduced a stripped upper camel case to remove the grossness in the generated code that was being forced upon the original source. See my convo with myself in #1919 😆 Still breaks client code; varname for a topic like |
c965c39
to
994c600
Compare
Now prescriptive about topic names. Breaks client code, so not merging yet. |
Fixes #1919