Releases: ydb-platform/yoj-project
Releases · ydb-platform/yoj-project
YOJ 2.2.19 (less radical deprecation warnings #2)
- #70: Less radical deprecation warnings for
Id.resolve()
YOJ 2.2.15-2 (backport less radical deprecation warnings no. 2)
- Backport less radical deprecation warnings for
Id.resolve()
(#70)
YOJ 2.2.15-1 (backport less loud deprecation warnings)
Backport to 2.2.15 (w/older Jackson dependency):
- Show warnings about
@Deprecated(forRemoval=true)
methods only once per JVM invocation, and only usingWARN
log level
YOJ 2.2.18 (less radical deprecation warnings)
- Show warnings about
@Deprecated(forRemoval=true)
methods only once per JVM invocation, and only usingWARN
log level
YOJ 2.2.17 (Jackson update)
Please use this release instead of 2.2.16.
- Update Jackson to
2.17.1
which has importantKotlinModule
fixes
YOJ 2.2.16 (dependency updates)
2.17.0
has serious regressions in its KotlinModule
. This module is not enabled in JacksonJsonConverter.getDefault()
but is typically enabled by Kotlin users of YOJ.
Please use version 2.2.17 instead.
- Bump Jackson 2.16.1->2.17.0 and AssertJ 3.25.1->3.25.3 (081ec6b)
YOJ 2.2.15 (API fix)
- #64: API FIX: Reinstate
FieldValue.of{Str,Num,Timestamp, ...}
methods aspublic
.
These methods offer explicit typing ofFieldValue
s, in contrast to the loosely typedFieldValue.ofObj(Object, JavaField)
.
In contrast,FieldValue.ofObj()
assumes that the value supplied is a valid field value, and applies theJavaField
's custom value typeValueConverter
to it, if it is defined. SomeValueConverters
, most notablyStringValueConverter
, accept anyObject
when converting Java value to DB column value; this coerces user-supplied value to aString
even if it was not intended to be used in that way.
YOJ 2.2.14 (more minor fixes)
- 92f99af -
ydb-repository-v2
: Don't use GuavaSuppliers.memoize()
inYdbRepository
. Also, don't reference GuavaSupplier
interface inyoj-util
YOJ 2.2.13 (bugfix and dependency update)
YOJ 2.2.5-3
More backports of fixes to 2.2.5