Philzen

@dthyresson According to the tutorial it should show exactly the error, as in the following picture (from that very tutorial):  How to make the graphql error that is visible...

@pantheredeye @Tobbe > It feels cleaner to address linting issues before code ever hits the main branch. That's exactly how i feel! Thanks for the RFC. I curated i list...

@kopestik as i wrote: > isRequired on FormControl works fine This issue is about this:  

> you need form-control when it is set to true. No, one doesn't *need* a FormControl to set it to true on those components – and it doesn't make *any...

Actually, on revisiting the Checkbox example, that description is also unclear: what is the expectation of "will be marked as required"? The only change i could see is a `required`-attribute...

Yo @stalebot, don't close, still an issue.

:+1:

@conclurer - Do you see any chance to review these and merge soon? I'd prefer not to have my fork linger around too long but to have these issues fixed...

Any chance to review this in 2016 :smiley: ?

:facepalm: Ahhh thanks @anubra266 for clarifying, now i see! Maybe we should make a note over at chakra-docs to clarify this in the props documentation?