Liero, the "N+1" comment was comparing GitHub's GraphQL API to the current GitHub API.
GraphQL and OData both provide means of avoiding N+1 queries.
One difference with GraphQL and OData is the query you send with GraphQL is formed as JSON in the request body rather than the OData format in the URL and defines the shape of the data you want back which is also returned as JSON. This is conceptually easier to manage for some.
But for these kind of querying scenarios, I believe both technologies to be pretty similar.
@Romeo When I said "Your stuff is broken" I was speaking to the StackOverflow team who was in the audience. As NickCraver points out (he's on the StackOverflow team), it was an output cache issue that made their site look different when I brought it up in IE 9.
Interesting how easy it is to have loose fingers when accusing someone of having a loose mouth. I generally like to give people the benefit of the doubt first and understand the context before making accusations. But that's just me.
@Dan no idea. I'll ask around.
@NickCraver I think it's awesome that you guys fixed it before my talk was over.
Good question. That was a bit of ignorance on my part. That attribute is System.ComponnentModel.DisplayNameAttribute which is part of System.dll. It is
a pre-existing attribute that we just happen to support and it wasn't designed with the localization features that our newer data annotations are designed with. Unfortunately, with
DisplayNameAttribute, the general idea is you have to subclass it to get localization. Yeah, that's annoying.
There are new attributes coming in ASP.NET 4 so I'll need to figure out what the suggested pattern will be.
All the validation components do allow setting resource keys such as ErrorMessageResourceType and