You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Oliver Drotbohm1:31 PM
Heads up: we've just merged a revamped implementation of the entire TypeInformation API now based on Spring's ResolvableType. All previous API is still intact, but we strongly encourage everyone to revisit their usage of ClassTypeInformationand its ….from(…) factory methods in particular. You should be able to replace those calls with TypeInformation.of(…) entirely and avoid referring to CTI at all. The mid-term goal is to hide it within the package, so that the only externally visible API is TypeInformation. If you find yourself struggling to achieve that, please reach out. The hiding move is planned for 3.1, but I'd love to get the official modules of the deprecated API for 3.0 already.
The text was updated successfully, but these errors were encountered:
Oliver Drotbohm 1:31 PM
Heads up: we've just merged a revamped implementation of the entire TypeInformation API now based on Spring's ResolvableType. All previous API is still intact, but we strongly encourage everyone to revisit their usage of ClassTypeInformationand its ….from(…) factory methods in particular. You should be able to replace those calls with TypeInformation.of(…) entirely and avoid referring to CTI at all. The mid-term goal is to hide it within the package, so that the only externally visible API is TypeInformation. If you find yourself struggling to achieve that, please reach out. The hiding move is planned for 3.1, but I'd love to get the official modules of the deprecated API for 3.0 already.
The text was updated successfully, but these errors were encountered: