@forzalabs/remora 2.6.0 → 2.7.0

package/json_schemas/consumer-schema.json

@@ -328,6 +328,17 @@
                                 "type": "integer",
                                 "minimum": 1,
                                 "description": "Optional 1-based column the field is expected to start at. Not a second source of truth — the offsets always come from the widths — but an assertion that compile recomputes and fails on, so a forgotten filler is caught where it is written."
+                            },
+                            "scale": {
+                                "type": "integer",
+                                "minimum": 1,
+                                "maximum": 15,
+                                "description": "'number' fields only. Implied decimal places this field is WRITTEN with, the way a COBOL 'PIC S9(7)V99' is: the point is dropped and the last 'scale' digits are the fraction, so 123.45 at scale 2 is written '0012345'. The write-side counterpart of the producer dimension's 'scale'; where both say the same thing, a read and write back is byte-identical."
+                            },
+                            "sign": {
+                                "type": "string",
+                                "enum": ["overpunch", "leading", "trailing"],
+                                "description": "'number' fields only. How this field carries its sign, for the layouts that do not simply write a leading '-'. 'overpunch' puts it in the last byte (-1231 is written '123J', +1231 as '123A'); 'leading'/'trailing' write a real '+' or '-' in the first or last column of the field. A positive value is written in the form the mode declares, never as bare digits."
                             }
                         }
                     }
@@ -396,7 +407,7 @@
                     "lineEnding": {
                         "type": "string",
                         "enum": ["lf", "crlf"],
-                        "description": "'FIXED' only. What ends every record, the last one included. Defaults to 'lf'. A real positional feed picks one and holds it — the NASCO POD files are CRLF on every line. A file with no terminator at all is fixed record framing (RECFM=FB) and is not expressible here."
+                        "description": "'FIXED' only. What ends every record, the last one included. Defaults to 'lf'. A real positional feed picks one and holds it — some are CRLF on every line. A file with no terminator at all is fixed record framing (RECFM=FB) and is not expressible here."
                     },
                     "layouts": {
                         "type": "object",

package/json_schemas/producer-schema.json

@@ -214,6 +214,19 @@
                     "type": "string",
                     "description": "Optional source format used when parsing/casting the value, e.g. a date format like 'YYYYMMDD' or 'DD-MM-YYYY'."
                 },
+                "scale": {
+                    "type": "integer",
+                    "minimum": 1,
+                    "maximum": 15,
+                    "description": "Implied decimal places of a 'number' field written WITHOUT a decimal point, the way a COBOL PIC S9(7)V99 is: the last 'scale' digits are the fraction, so '0012345' at scale 2 reads as 123.45. A field written with its decimal point, or with no fraction at all, omits this. 'number' dimensions only.",
+                    "examples": [2]
+                },
+                "sign": {
+                    "type": "string",
+                    "enum": ["overpunch", "leading", "trailing"],
+                    "description": "How a 'number' field written as text carries its sign, for layouts that don't simply write a leading '-'. 'overpunch': the last byte carries the sign as well as its digit, the way a signed COBOL DISPLAY field does, so -1231 is written '123J' ('{' and 'A'-'I' positive, '}' and 'J'-'R' negative, a plain digit positive). 'leading'/'trailing': a real '+' or '-' in the first or last position. 'number' dimensions only.",
+                    "examples": ["overpunch"]
+                },
                 "alias": {
                     "type": "string",
                     "description": "The SQL column or field key that corresponds to this dimension. If left empty, the column name is assumed to be the same as the dimension name."
@@ -263,10 +276,10 @@
                     "type": "array",
                     "minItems": 1,
                     "items": { "$ref": "#/definitions/dimension" },
-                    "description": "Makes this a repeating GROUP of fields (a COBOL OCCURS segment): the fields that repeat, each 'position' RELATIVE to one occurrence. The group's own 'position' is the extent of ONE occurrence, so its 'length' is the bytes per occurrence, not the whole group's span. Expanded into one dimension per (occurrence x child) when the config loads, so nothing downstream sees a group. A group declares no 'type' and produces no column of its own. FIXED producers only; nested groups are not supported yet."
+                    "description": "Makes this a repeating GROUP of fields (a COBOL OCCURS segment): the fields that repeat, each 'position' RELATIVE to one occurrence. The group's own 'position' is the extent of ONE occurrence, so its 'length' is the bytes per occurrence, not the whole group's span. Expanded into one dimension per (occurrence x child) when the config loads, so nothing downstream sees a group. A group declares no 'type' and produces no column of its own. Groups nest, the way a copybook's OCCURS clauses do: a child may be a group in turn, positioned RELATIVE to one occurrence of the group it sits in and with all of its own occurrences inside that one. A nested group repeats a fixed number of times and cannot declare 'emit'. FIXED producers only."
                 },
                 "occurs": {
-                    "description": "How many times a group's fields repeat. An integer when every line has the same count — default 1, so a group is also usable purely to structure a non-repeating segment. An object when the count VARIES line by line: the group still generates 'max' columns (a line with fewer reads them as null), and everything after it must be anchored with 'position.after' because the group's span differs per line.",
+                    "description": "How many times a group's fields repeat. An integer when every line has the same count — default 1, so a group is also usable purely to structure a non-repeating segment. An object when the count VARIES line by line: the group still generates 'max' columns (a line with fewer reads them as null), and everything after it must be anchored with 'position.after' because the group's span differs per line. The limit of 1000 applies per level, so a nested group is bounded at the product. A nested group takes the integer form only.",
                     "oneOf": [
                         {
                             "type": "integer",
@@ -324,10 +337,16 @@
                     "description": "On an 'emit': 'rows' group: the name of the generated field holding the occurrence index. Default '{group}Occurrence'.",
                     "examples": ["addr_occurrence"]
                 },
+                "usage": {
+                    "type": "string",
+                    "enum": ["display", "comp", "comp-3"],
+                    "description": "How the source system STORES this field, as a COBOL copybook's USAGE clause declares it. Written by 'remora import-copybook'. 'display' is characters and is the only one a positional read can address; 'comp' (binary) and 'comp-3' (packed decimal) hold their digits as bytes and are rejected at compile, naming the field, so the feed is converted to display before it is sent rather than read as NaN.",
+                    "examples": ["comp-3"]
+                },
                 "naming": {
                     "type": "string",
                     "minLength": 1,
-                    "description": "Template for the dimension names generated by a group or by 'flags'. On a group the tokens are {group}, {index}, {field} and {Field} (capitalized), and {index} is required unless 'occurs' is 1; default '{group}{index}{Field}'. On a 'flags' dimension they are {field}, {Field}, {flag} and {Flag}, one flag token required; default '{field}{Flag}'.",
+                    "description": "Template for the dimension names generated by a group or by 'flags'. On a group the tokens are {group}, {index}, {field} and {Field} (capitalized), and {index} is required unless 'occurs' is 1; default '{group}{index}{Field}'. Each level of a nested group names what the level below it generated, so the default gives 'addr0Phone1Area'; {index1}...{indexN} reach N levels outward from the group's own {index}. On a 'flags' dimension the tokens are {field}, {Field}, {flag} and {Flag}, one flag token required; default '{field}{Flag}'.",
                     "examples": ["{group}{index}{Field}", "{group}_{index}_{field}", "{field}_{flag}"]
                 },
                 "flags": {

package/package.json

@@ -1,6 +1,6 @@
 {
     "name": "@forzalabs/remora",
-    "version": "2.6.0",
+    "version": "2.7.0",
     "description": "A powerful CLI tool for seamless data translation.",
     "main": "index.js",
     "private": false,
@@ -44,7 +44,7 @@
         "typescript"
     ],
     "author": "",
-    "license": "BSL",
+    "license": "SEE LICENSE IN LICENCE.md",
     "dependencies": {
         "@aws-sdk/client-redshift-data": "^3.699.0",
         "@aws-sdk/rds-signer": "^3.1136.0",