Hugh Gleaves

> @Korporal with [that](https://github.com/LtiLibrary/LtiLibrary/issues/137#issuecomment-829286185) and ignoring case being rather controversial, like #23, and the long time passed, I'll also close this as wontfix now. That makes total sense @jeroenhabets, thanks...

@srijken - Hi. Well this [project ](https://github.com/LtiLibrary/LtiAdvantage/blob/master/src/LtiAdvantage.AspNetCore/LtiAdvantage.AspNetCore.csproj) actually also targets .Net Core 3.1 that's what I'm referring to. Also the dependency on Newtonsoft is undesirable, In a world where we'll...

Regarding field access, it seems that there must be a non-breaking way to address this, perhaps: ```cs public class Professor { private string field; public string Field { get =>...

So why is this _not_ allowed then? ```cs var attributes_func = context.declarationBody()?.typeInfo()?.attribute; ``` The last element `attribute` is a method just like `declarationBody` and `typeInfo`. This generates CS8978