Open remyleone opened 2 years ago
@remyleone The reason it fails is because the type has to be exported, hence start with uppercase in Go. But it's a great idea to have a validation since it's not clear that this is the problem. Maybe here after all configurators are run?
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
What happened?
I've used a configurator like this:
The problem is that it created issue in angryjet like this:
I've fixed it using
IP
instead ofip
. Maybe it could be a good idea to add validation on the r.Kind field about the convention for kind (uppercased, lowercase, camelcase, ...)How can we reproduce it?