lex45x / queryninja Goto Github PK

This will solve tons of issues, including flattening the learning curve for QueryNinja.

GraphQL support will be only partial and will cover only features present in Release v1.1.
Especially:

• Filtering
• Sorting
• Selecting

GraphQL schema generation will be supported to allow usage of external GraphQL editors.

Challenges:

• Implement deserialization for IQuery and IDynamicQuery (IDefaultFilter).
• Implement type name introspection kind of selector. https://spec.graphql.org/June2018/#sec-Type-Name-Introspection
• Integrate Altair editor in the QueryNinja.Source.GraphQL package.
• ⚠️ Design schema extensions that will allow defining filters and ordering rules. The introspection Query has to be updated accordingly.
• Introspection Query should serve all available action methods and types.
• Implement deserialization for IQuery and IDynamicQuery (selectors only for now).
• Add ability to call entity method via a selector. It is needed to allow method calls from GraphQL.
• Allow default selectors to work across collection properties.
• Core needs to provide attributes to describe the target type of IQueryComponent. This information will be used to build Schema.
• IQuery and IDynamicQuery should become generic to represent the target model type. Queryable Target should be updated as well.
• We need to build a GraphQL interpreter that can create IQuery instances from the query. Can reuse existing parser

Usage of Asp.Net Core Controllers to maintain queries might be misleading. These action items might be changed in the future.

• Scan Asp.Net Core application and find all action methods that are using IQuery<> parameter and build Types map.
• Each action method should represent an available set of data.
• Deserialized query then should be passed to controller instance. (Use IControllerFactory from Asp.Net Core)

Extend existing IQueryable target with EF-specific features like EF.Functions, etc.