2026.05.13¶
Bump
literalizerto 2026.5.13.1. The new release re-exposes thesupports_*class attributes forempty_dict_key,call_style, and the fivedefault_*_typeoptions, restoring a type-safe probe for runtime-dispatched constructor kwargs (cf. upstream issue #2147).Replace
--line-endingwith--statement-terminator-style. The upstreamLineEndingsenum was removed;StatementTerminatorStyles(semicolon,none) is its successor.Add
--call-stylefor picking between per-language call shapes (e.g.curriedfor Haskell / OCaml / F# / SML / Elm,namedfor Visual Basic).Add
--numeric-stylefor languages that support multiple numeric rendering styles (e.g.overloadedvs.explicit).Add
--language-versionfor selecting the target language version (each language exposes aVersionFormatsenum).Add
--module-namefor languages whose--wrap-in-fileform defines a scope with a name (C, C++, D, Erlang, Fortran, F#, Java, Objective-C, Occam, SystemVerilog). Previously amodule_nameargument toliteralizeitself, now a per-language constructor argument.Add
--ref-keyfor picking a marker key other than$reffor variable-reference mappings in the input data.Surface the new typed
literalizerexceptions as clean CLI errors rather than tracebacks:UnsupportedCallShapeError,VariableNameNotSupportedError,WrapInFileWithoutVariableNotSupportedError,WrapCombinedInFileNotSupportedError,DottedCallTargetNotSupportedError,DottedCallStubNotSupportedError,FreeFunctionCallNotSupportedError,CallArgNotSupportedError,HeterogeneousScalarCollectionError,UnrepresentableSpecialFloatError.--variable-type-hints autois now--variable-type-hints never(upstream rename), with a newsafeoption that annotates only when the language’s own inference would widen the variable to a permissive type (e.g.unknown[]for an empty TypeScript array).