Scott

I need to report, I've now got Ubuntu Desktop running (switched from Windows for better dev experience) and as a nice side-effect Lens and the Resource Map Extension are working...

Other packages I'm using have made the v16 upgrade, but I can't use their newer versions, because Nest-graphql hasn't been upgraded to v16 yet. Would be great, if it would...

> I should be able to define input fields with a default value AND make them required to prevent them from accepting the value null as user input. This isn't...

@Haltarys - I see what you are getting at. And my comment above is also incorrect. "null" is a value in the end. My understanding is, as soon as a...

I see what you mean, but wanting a non-nullable field with a default still makes no sense to me. [The spec even says](https://spec.graphql.org/June2018/#sec-Type-System.Non-Null), non-null fields are required and shouldn't accept...

I think even the GraphQL spec has been changed (or I seriously overlooked it). > In addition to not accepting the value **null**, it also does not accept omission. For...

Just so I understand this better. Do you want appserver to do more to help device detection? In other words, instead of leaving it up to the client developer, appserver...

Ah ok. But, the header is dissected. The device detection is just additional logic to help tell the application what device is being used. Got it. Thanks. Scott

Being my picky self, I'd have to raise my finger and say the second point isn't written from the user's perspective. Or rather, it isn't a point a user could...

Thanks for the explanation. I understand now, for the most part. Scott