Files
dc/client
dc 33d043ea92
Build / Build-and-ng-test (pull_request) Successful in 5m15s
Lighthouse Checks / lighthouse (pull_request) Successful in 20m15s
Build / Build-and-test-development (pull_request) Successful in 31m0s
feat(derived): VARIABLE_ORDER, so a derived variable can build on another
A derived variable may need to reference one defined before it (a label that
concatenates a derived region, for example), so the order has to be
configured rather than assumed.

- MPE_DERIVED: new VARIABLE_ORDER column (ddl, makedatamodel, migration).
- mpe_derived: statements are generated in VARIABLE_ORDER then name sequence.
  VARIABLE_ORDER is required and must be a positive integer. A reference to a
  derived variable with an equal or higher order is rejected, because SAS
  would otherwise treat it as uninitialised and return a missing value with no
  error; references to lower-order variables are allowed.
- mock: same ordering, each variable compiled against the physical columns
  plus those defined earlier, so the frontend can exercise a chained variable.
- makedata: VARIABLE_ORDER on both demo rows plus a chained REGION_LABEL.
- cypress: asserts the chained value in the grid.
- tests: the getdata test seeds a second variable built on the first.
- docs: VARIABLE_ORDER documented, with the ordered rule replacing the
  self-contained one.
2026-10-20 02:09:37 +00:00
..
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00
2026-05-25 13:29:27 +02:00
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00
2023-07-13 13:44:05 +02:00
2024-05-02 13:08:06 +02:00