v6.0.0 #484
oojacoboo
announced in
Announcements
v6.0.0
#484
Replies: 1 comment 1 reply
-
👋 Hi, At least if we can have information if something is blocking, just to know how to handle it :) Thanks for your awesome work, and your time on this subject 🙏 |
Beta Was this translation helpful? Give feedback.
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hurrah version 6 landing! There is a lot in this one and it's long overdue, but we finally hit a great spot, so without further adieu.
Version 6 brings
#[Input]
defined InputTypes way forward and solidifies their overall functionality.#[Input]
attribute defined InputTypes are becoming my preferred way of defining these types. One single DTO or even Doctrine entity (if you so dare!) can be used to define both input and output types, with virtually no side-effects or missing feature functionality. Prior to version 6,#[Input]
defined types were rather limited. This is no longer the case! If you haven't had a chance yet, now is the time to give them a spin! 👍 A special thanks to @Lappihuan for all his teamwork on the InputType improvements. This wouldn't have happened without him!In addition to the huge improvements made on InputTypes, we now have support for native Enums, union return typing, and generics support!
Dependencies:
Breaking Change:
#458 With
Input
annotated InputTypes, if you're using the same class for multiple types, like an update type and create type (also now a possibility), if you provide a name, you must also provide thedefault
parameter if you want the InputType to be the "default".New Features:
#409 Native Enum support! 🎉
#467 Support native union return typing
#468 Support generic phpdpc style typed interables for output type values
#435 New Custom InputType Validator offering flexibility in how you can handle validation on all of your
#[Input]
attributes.#458 Recursive InputType resolving
#466 Bring existing getter
#[Field]
defined functionality from output#[Type]
objects to InputType annotated fields, via setters.This discussion was created from the release v6.0.0.
Beta Was this translation helpful? Give feedback.
All reactions