ng-form-foundry-transformers 0.3.1 → 0.3.2

package/README.md

@@ -43,6 +43,12 @@ For config formats (YAML, JSON) the thing you load and save is the same document
 type, so `TData` defaults to `TSource`. Schema formats differ: YANG's `toSchema`
 consumes a model source but its `toSource` reverts to RFC 7951 *data*.
 
+**Choice values:** the YAML/JSON `toSource` applies the value's keys verbatim,
+so when the schema contains choices (`anyOf`/`oneOf`) pass the **wire value** —
+the library's `serializeForm(schema, form)`, which strips the `__case`
+discriminators from `getRawValue()`. The YANG adapter is the exception: its
+`toYangData` consumes the form value and flattens `__case` itself.
+
 ## YAML transformer
 
 Edit a **YAML config file**: turn it into a form, then write the edited value
@@ -181,6 +187,10 @@ npm test        # node:test on the compiled output (no Python needed)
 
 ## Status
 
+`0.3.2` — documentation release alongside the library's `serializeForm`: the
+YAML/JSON `toSource` examples now take the wire value (choice `__case`
+discriminators stripped); no transformer code changes.
+
 `0.3.1` — version alignment with the library's review-fix release (all 59
 findings of the tree-editor/form-renderer review resolved); no transformer
 changes.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "ng-form-foundry-transformers",
-  "version": "0.3.1",
+  "version": "0.3.2",
   "description": "Framework-agnostic Node + TypeScript catalog of source-format transformers: turn a YANG model (and more) into an ng-form-foundry schema and revert the edited form value back to the source format.",
   "keywords": [
     "ng-form-foundry",