Suppose you cut Wolverine in half, top to bottom. What happens:
A) Half dies, other half lives
B) Both regenerate into new Wolverine
C) Half dies, other half lives, but the regenerated Wolverine has problems related to having two right or two left hemphispheres
D) Both regenerate, but with the problem described in C.
and you still can't customise or collapse ui elements like Fireworks could. I never use Layout Constraints, why do I always have to scroll to see the stuff I do use?
I know naming is hard, but h for 'response toolkit' is pretty poor
> Unlike Express, which has a handler with parameters of req and res, hapi has a handler with parameters of request and h. The second parameter, h is the response toolkit, which is an object with several methods used to respond to the request.
It's unclear whether it passes wcag but from our research I think it's much clearer to mark optional fields as 'optional' than have asterisks or 'required' next to every field and have optional fields implied by the lack of them.
If you're asking for data, the default should be it's because it is required. This is part of GDPR
@siblingpastry Hmm I can see that interpretation, but I don't think it's explicit in name, role and value to convey required, and certainly in practice it is conveyed
@siblingpastry Thanks, it's an interesting topic. I think maybe part of it is I think it would have been better from the start to mandate indicating optional , but that's not where we are
@siblingpastry Oh personally and from using it a lot on gov.uk I think highlighting only optional is the better pattern. It's hard to know how much of that is our context and our other patterns like One thing per page