Tags: commercetools/scraml
Tags
Add key based discriminator annotation (#59) * add key based discriminator anntation * fix imports * fix scala format * fix failed tests * fix string type in term select * use fold instead of orElse * small refactor * change to use a map of values at trait level
(gen): add generator parameter for default variant (#58) * (gen): add generator parameter for default variant this allows for forward compatible enums and other scenarios where new/invalid enums should not fail the whole decoding * add setting --------- Co-authored-by: cristiborta <cristian.borta@commercetools.com>
(gen): fix leaf types aggregation (#49) Currently, in the leaf type aggregation, some intermediate types might end up in the result set because RMF creates subtypes on usages in properties. That is also the reason for the current names filter but it is not sufficient in all cases. This can lead to unreachable code in the decoders. With this change, we make sure the types we iterate through are API-level types. As a consequence, we might have some types that were previously intermediate types because they have (only) property subtypes. Those are considered leaf types now if the filtered subtypes set is empty. + update raml-model and related fixes
Enhance TapirSupport to support non-string Params property types (#48) * (fix): Scaladoc class description content When the '(docs-uri)' custom annotation is not present on a DataType, the top-level 'description' content is used if provided. This fix ensures that the content emitted is not the result of 'DescriptionFacet.toString'. * (fix): Resource name generation with more than one param * (gen): use uriParameters types in tapir path params * (test): Fix 'tapir-complex' resource URI definition Tapir does not support optional path segments, thus making the previous 'tapir-complex.raml' 'delay?' definition illegal. See https://tapir.softwaremill.com/en/latest/endpoint/codecs.html#optional-and-multiple-parameters .
PreviousNext