Release 1.12.0

[rmosolgo]

This is a checklist and tracking issue for the next release of GraphQL-Ruby.

• Rails-style validations for inputs (Better arguments and inputs validation #799, Rails-style validations for inputs #3164, Rails-like argument validation #3207) :
  • min/max length (strings, lists)
  • min/max (integer, float)
  • pattern (strings)
  • in (set of values, inclusion and exclusion)
  • not null (for required inputs -- to avoid explicitly-given null)
  • custom validation docs
  • custom message options
• Parallelizable data loader GraphQL::Dataloader, built-in batching system #2483 Add fiber-based batch loading API #3264
• Immutable arguments objects Make Interpreter::Arguments immutable #3004
• Extract connection/edge type behaviors into modules Pagination docs feedback #2542 Extract relay connection to module #3071
• First-class support for field directives No way to specify a directive on a field definition #2122, Directive definition support #3143, PR: First-class schema directives #3224
• The library defaults to new behaviors Default to Interpreter, Analysis::AST, Execution::Errors and Pagination::Connections #3145
  • Interpreter
  • Analysis::AST
  • Pagination::Connections
  • Execution::Errors
• Deprecate everything that will be removed in GraphQL-Ruby 2.0, remove docs for them Add lots of deprecations for 2.0 #3275
  • .define, old type classes, old field and argument classes
  • SerialExecution, GraphQL::Execution::Execute, Query::ArgumentsCache (because interpreter has a new one)
  • Old Relay helpers (connections, mutation, node Id)
  • Old execution extension points: field instrumentation, middleware
  • Irep & irep analysis
  • GraphQL::Compatibility -- no external runtimes are supported, no external parsers are supported (libgraphqlparser-ruby hasn't worked since 1.9.x)
  • Rework execution to bypass executor?
  • Schema::Validation
  • Schema::Upgrader, Railtie
  • Schema instance behaviors (associated with .define-returned instances)
  • GraphQL::Function
  • GraphQL::BackwardsCompatibility (which was for .define)
  • GraphQL::DeprecatedDSL
  • Legacy validator classes with .validate
  • SCREAMING_CASE scalar type constants
  • Multiplex#run_one_legacy etc
  • more?

[newx]

@rmosolgo if you could provide more info about the remaining TODO items, I could try to help working on some of them :)

[rmosolgo]

👋 @newx ! A couple of the big features already have open PRs. I just need to wrap those up.

Besides that, all the parts of graphql-ruby listed above need to have deprecation warnings because they'll be removed in GraphQL-Ruby 2.0. I'm not really sure what needs to be done there. We need something that will warn reliably without spamming the logs with warnings.

I think warn "..." would be sufficient, as long as each warning includes:

• What thing is deprecated
• Where the deprecated thing is being used (some part of caller, so that the reader knows what lines of their own code to change)
• What thing to use instead of the deprecated thing (including a usage example and/or link to documentation)

The goal is for the deprecation warning to be so good that someone who sees it can make the required change without opening an issue on github (or maybe even without searching the docs!).

If you're interested in adding some of those, feel free to pick a few items off the list and open a PR. That way we can make sure the messaging aligns with my goals above before you add a lot of them.

There will also be some work in updating GraphQL-Ruby's own code and tests to make sure those deprecated things are not used. In my opinion, that can be done after adding the warnings. (Besides, GraphQL-Ruby's own deprecated usage can help us make sure the warnings work 😆 !)

[newx]

@rmosolgo Cool. I will take a look at these and get back to you soon. Thank you

[rmosolgo]

🚢 !