Goa not enforcing required attribute about goa HOT 6 OPEN

I believe what's happening here is that the Goa generated CLI uses the service type to load the JSON passed on the command line. Because the attribute is required the corresponding field does not use a pointer and so defaults to 0. So the server gets an object with the field set to 0, it is not missing and validation does not fail. To convince yourself use another client tool (e.g. httpie) that won't initialize required fields to their zero value if not explicitly defined.

from goa.

That was what I was afraid was happening - is there a way to avoid this besides not using goa? I feel like I'm missing something because this makes it seem like having a Required type isn't possible with a goa cli/server combo?

from goa.

This is just the CLI code behaving that way when loading bodies from the JSON in the terminal - not the underlying server or client packages so any service making use of these packages won't have this issue.

from goa.

Understood, but one of the reasons I'd like to use goa is that it will generate both the cli and server for me. Having to write/maintain a CLI separately from the goa-generated one is taking away one of the main selling points for me. I will look into some of the other validation functions to see if I can work around it in the short term, but would love to see if there is a better long term fix.

Similar to #687

from goa.

Makes sense, I'd be happy to consider / help putting together a PR that improved this. We may need to generate special types for the CLI instead of relying on the existing service level types to perform that kind of validation.

from goa.

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs.

from goa.