@balena/pinejs 16.0.0-build-fisehara-update-sbvr-types-cfbbecbb0387e87e17e14be8991be73d1a4efdd0-1 → 16.0.0-build-fisehara-update-sbvr-types-f5e8e6ebfd0d3f590ef6ed3fa6b46d1b0861d409-1

package/.versionbot/CHANGELOG.yml

@@ -1,13 +1,18 @@
 - commits:
-    - subject: Update @balena/sbvr-types major
-      hash: cfbbecbb0387e87e17e14be8991be73d1a4efdd0
+    - subject: Update `@balena/sbvr-types` to enable ISODatestring as internal pine
+        API interface for date and date time fields.
+      hash: f5e8e6ebfd0d3f590ef6ed3fa6b46d1b0861d409
       body: >
         Update `@balena/sbvr-types` from 6.1.1 to 7.0.1
 
 
-        pinejs provides an internal and external interface. The external interface returns ISODateString encoded data.
+        pinejs provides an internal and external interface. The external
+        interface returns ISODateString encoded data.
 
-        The internal interface should be consistent to the external interface, so that the pinejs api internally used also returns an ISODateString encoded data. This is solved in `sbvr-types` and is a major in the submodule and made this also a major change for pinejs itself.
+        The internal interface should be consistent to the external interface,
+        so that the pinejs api internally used also returns an ISODateString
+        encoded data. This is solved in `sbvr-types` and is a major in the
+        submodule and made this also a major change for pinejs itself.
 
 
         https://github.com/balena-io-modules/sbvr-types/pull/91
@@ -20,7 +25,7 @@
       nested: []
   version: 16.0.0
   title: ""
-  date: 2024-03-06T08:27:29.829Z
+  date: 2024-03-08T13:37:27.895Z
 - commits:
     - subject: "Tests: Remove restart=always policy for sidecar containers"
       hash: 70d46bc6ccf970a2750a5a92cb2331f168790507
@@ -190,7 +195,8 @@
                       body: >
                         - Update @balena/lint from 6.2.2 to 7.2.4
 
-                        - Delete `require-npm4-to-publish` as handled by `engines` parameter in `package.json`
+                        - Delete `require-npm4-to-publish` as handled by
+                        `engines` parameter in `package.json`
                       footer:
                         Change-type: patch
                         change-type: patch
@@ -279,7 +285,8 @@
               body: >
                 - Update @balena/lint from 6.2.2 to 7.2.4
 
-                - Delete `require-npm4-to-publish` as handled by `engines` parameter in `package.json`
+                - Delete `require-npm4-to-publish` as handled by `engines`
+                parameter in `package.json`
               footer:
                 Change-type: patch
                 change-type: patch
@@ -519,7 +526,8 @@
                         Ensure that the input passed in for JSON types is either
                         an object or
 
-                        an array (typeof returns 'object' for arrays as well). This change is
+                        an array (typeof returns 'object' for arrays as well).
+                        This change is
 
                         mainly to prevent primitives from being stored as JSON.
                       footer:
@@ -945,9 +953,11 @@
                                         Ensure that the input passed in for JSON
                                         types is either an object or
 
-                                        an array (typeof returns 'object' for arrays as well). This change is
+                                        an array (typeof returns 'object' for
+                                        arrays as well). This change is
 
-                                        mainly to prevent primitives from being stored as JSON.
+                                        mainly to prevent primitives from being
+                                        stored as JSON.
                                       footer:
                                         Change-type: major
                                         change-type: major
@@ -1087,7 +1097,8 @@
                                         We know what type they return and they
                                         should be explicitly accepted as
 
-                                        those types instead where it is valid to do so
+                                        those types instead where it is valid to
+                                        do so
                                       footer:
                                         Change-type: patch
                                         change-type: patch
@@ -1495,9 +1506,11 @@
                                 Ensure that the input passed in for JSON types
                                 is either an object or
 
-                                an array (typeof returns 'object' for arrays as well). This change is
+                                an array (typeof returns 'object' for arrays as
+                                well). This change is
 
-                                mainly to prevent primitives from being stored as JSON.
+                                mainly to prevent primitives from being stored
+                                as JSON.
                               footer:
                                 Change-type: major
                                 change-type: major
@@ -1625,9 +1638,11 @@
                                 Ensure that the input passed in for JSON types
                                 is either an object or
 
-                                an array (typeof returns 'object' for arrays as well). This change is
+                                an array (typeof returns 'object' for arrays as
+                                well). This change is
 
-                                mainly to prevent primitives from being stored as JSON.
+                                mainly to prevent primitives from being stored
+                                as JSON.
                               footer:
                                 Change-type: major
                                 change-type: major
@@ -1896,7 +1911,8 @@
         https://github.com/brianc/node-postgres/pull/2967
 
 
-        In pinejs the case is handled and as of now we don't want to populate a breaking change by transparently push the types to callers.
+        In pinejs the case is handled and as of now we don't want to populate a
+        breaking change by transparently push the types to callers.
       footer:
         Change-type: patch
         change-type: patch
@@ -2100,9 +2116,11 @@
       body: >
         On empty database schemas the `migrations` model is not executed.
 
-        Hence, every model migration that is executed before the `migrations` model
+        Hence, every model migration that is executed before the `migrations`
+        model
 
-        will not be tracked properly. This is an edge case for empty database schemas.
+        will not be tracked properly. This is an edge case for empty database
+        schemas.
       footer:
         Change-type: patch
         change-type: patch
@@ -2633,9 +2651,11 @@
                                 Ensure that the input passed in for JSON types
                                 is either an object or
 
-                                an array (typeof returns 'object' for arrays as well). This change is
+                                an array (typeof returns 'object' for arrays as
+                                well). This change is
 
-                                mainly to prevent primitives from being stored as JSON.
+                                mainly to prevent primitives from being stored
+                                as JSON.
                               footer:
                                 Change-type: major
                                 change-type: major
@@ -3179,7 +3199,8 @@
                         Ensure that the input passed in for JSON types is either
                         an object or
 
-                        an array (typeof returns 'object' for arrays as well). This change is
+                        an array (typeof returns 'object' for arrays as well).
+                        This change is
 
                         mainly to prevent primitives from being stored as JSON.
                       footer:
@@ -3333,7 +3354,8 @@
                         Ensure that the input passed in for JSON types is either
                         an object or
 
-                        an array (typeof returns 'object' for arrays as well). This change is
+                        an array (typeof returns 'object' for arrays as well).
+                        This change is
 
                         mainly to prevent primitives from being stored as JSON.
                       footer:
@@ -3452,7 +3474,8 @@
                 Ensure that the input passed in for JSON types is either an
                 object or
 
-                an array (typeof returns 'object' for arrays as well). This change is
+                an array (typeof returns 'object' for arrays as well). This
+                change is
 
                 mainly to prevent primitives from being stored as JSON.
               footer:
@@ -5097,46 +5120,60 @@
                         After every write, pine has to rerun all rules from the
                         model to ensure
 
-                        consistency. These rules run over the entire database, sometimes causing
+                        consistency. These rules run over the entire database,
+                        sometimes causing
 
-                        some queries to run for too long against what should be a simple write.
+                        some queries to run for too long against what should be
+                        a simple write.
 
 
-                        This commit adds a mechanism to help with this issue by narrowing the
+                        This commit adds a mechanism to help with this issue by
+                        narrowing the
 
-                        set of rows that each rule should touch to those rows that were actually
+                        set of rows that each rule should touch to those rows
+                        that were actually
 
                         changed.
 
 
-                        Implementing this mechanism safely is doable and not necessarily complex
+                        Implementing this mechanism safely is doable and not
+                        necessarily complex
 
-                        code-wise, but requires a deep modifications from the current
+                        code-wise, but requires a deep modifications from the
+                        current
 
-                        architecture. This commit adds a restricted form instead where we only
+                        architecture. This commit adds a restricted form instead
+                        where we only
 
-                        narrow the rows of the root table that were changed. If any other table
+                        narrow the rows of the root table that were changed. If
+                        any other table
 
                         was changed then narrowing is a no op.
 
 
-                        It can be proved that this is always safe as long as the root table is
+                        It can be proved that this is always safe as long as the
+                        root table is
 
-                        selected from only once and the rule is positive ("It is necessary that
+                        selected from only once and the rule is positive ("It is
+                        necessary that
 
                         each ...").
 
 
-                        The implementation here adds a single binding into the rule's SQL query
+                        The implementation here adds a single binding into the
+                        rule's SQL query
 
-                        which can be bound by pine for each rule where an opportunity to use
+                        which can be bound by pine for each rule where an
+                        opportunity to use
 
                         this optimization arises.
 
 
-                        The implementation itself is simple: count how many times the root table
+                        The implementation itself is simple: count how many
+                        times the root table
 
-                        is selected from and if it is selected from exactly one, then add a
+                        is selected from and if it is selected from exactly one,
+                        then add a
 
                         narrowing constraint in the form of:
 
@@ -5146,12 +5183,14 @@
                         <root table>.id = ANY(CAST($1 AS INTEGER[]))
 
 
-                        Where $1 will be bound to either '{}', which disables narrowing, or to a
+                        Where $1 will be bound to either '{}', which disables
+                        narrowing, or to a
 
                         list of IDs that were affected by the write.
 
 
-                        This initial implementation can be extended in the future.
+                        This initial implementation can be extended in the
+                        future.
                       footer:
                         Change-type: major
                         change-type: major
@@ -5172,7 +5211,8 @@
                 This function can get called a lot so caching it should provide
                 a
 
-                noticeable performance improvement and linking it to the resource makes
+                noticeable performance improvement and linking it to the
+                resource makes
 
                 cache management simple
               footer:
@@ -5220,7 +5260,8 @@
         This reverts commit 6b85dd0063669e7db4432bdb650927d05ef9f9c4.
 
 
-        Pin grunt to fixed 1.5.3 as grunt does not follow semver. Needed for now to executed on node12
+        Pin grunt to fixed 1.5.3 as grunt does not follow semver. Needed for now
+        to executed on node12
       footer:
         Change-type: minor
         change-type: minor
@@ -5343,11 +5384,14 @@
                 This increases the minimum postgres version for AggregateJSON
                 from 9.2
 
-                to 9.3 but it is likely that other places already require postgres
+                to 9.3 but it is likely that other places already require
+                postgres
 
-                >=9.3 and as such this should not increase the minimum version at all.
+                >=9.3 and as such this should not increase the minimum version
+                at all.
 
-                If it does somehow manage to then increasing the minimum from a 2012
+                If it does somehow manage to then increasing the minimum from a
+                2012
 
                 postgres to 2013 should still be fine
               footer:
@@ -5428,7 +5472,8 @@
                 This is intended to be used to target tables differently for
                 reads vs
 
-                writes, eg where you might read from a view/definition but want to
+                writes, eg where you might read from a view/definition but want
+                to
 
                 write to a physical table instead
               footer:
@@ -5469,7 +5514,8 @@
               body: >
                 `lfInfo` will be used to pass extra context extracted from LF
 
-                downstream. Currently the only context is the root table alias for each
+                downstream. Currently the only context is the root table alias
+                for each
 
                 rule.
               footer:
@@ -5489,7 +5535,8 @@
                 This is intended to be used to target tables differently for
                 reads vs
 
-                writes, eg where you might read from a view/definition but want to
+                writes, eg where you might read from a view/definition but want
+                to
 
                 write to a physical table instead
 
@@ -5507,7 +5554,8 @@
                         This is intended to be used to target tables differently
                         for reads vs
 
-                        writes, eg where you might read from a view/definition but want to
+                        writes, eg where you might read from a view/definition
+                        but want to
 
                         write to a physical table instead
                       footer:
@@ -5634,7 +5682,8 @@
                 This avoids issues where the aliases may not map up,
                 particularly if
 
-                the definition was generated and may have automatic aliases, eg if
+                the definition was generated and may have automatic aliases, eg
+                if
 
                 using the result of an odata-to-abstract-sql generation
               footer:
@@ -6403,7 +6452,8 @@
                 if operands in expression can be used as numericValues.
 
 
-                In SQL statements arithmetic expressions like add/sub are supported for date values.
+                In SQL statements arithmetic expressions like add/sub are
+                supported for date values.
 
                 DateArithmetic nodes need input dependent typing.
               footer:
@@ -6449,12 +6499,15 @@
                                 isNumericValue is evaluated in arithmetic
                                 expressions
 
-                                if operands in expression can be used as numericValues.
+                                if operands in expression can be used as
+                                numericValues.
 
 
-                                In SQL statements arithmetic expressions like add/sub are supported for date values.
+                                In SQL statements arithmetic expressions like
+                                add/sub are supported for date values.
 
-                                DateArithmetic nodes need input dependent typing.
+                                DateArithmetic nodes need input dependent
+                                typing.
                               footer:
                                 Change-type: minor
                                 change-type: minor
@@ -6831,7 +6884,8 @@
                         if operands in expression can be used as numericValues.
 
 
-                        In SQL statements arithmetic expressions like add/sub are supported for date values.
+                        In SQL statements arithmetic expressions like add/sub
+                        are supported for date values.
 
                         DateArithmetic nodes need input dependent typing.
                       footer:
@@ -7365,7 +7419,8 @@
         when I is not set in the overload.
 
 
-        tsc 4.8 https://devblogs.microsoft.com/typescript/announcing-typescript-4-8/#unconstrained-generics-no-longer-assignable-to
+        tsc 4.8
+        https://devblogs.microsoft.com/typescript/announcing-typescript-4-8/#unconstrained-generics-no-longer-assignable-to
       footer:
         Change-type: patch
         change-type: patch
@@ -7956,12 +8011,15 @@
                                 'strict' or 'informative'.
 
 
-                                Behaviour change only if type is informative otherwise default 'strict'.
+                                Behaviour change only if type is informative
+                                otherwise default 'strict'.
 
 
-                                An informative reference is just an int field that points
+                                An informative reference is just an int field
+                                that points
 
-                                to another tables id field - like foreign key without constraints
+                                to another tables id field - like foreign key
+                                without constraints
 
                                 or foregein key cascades.
                               footer:
@@ -7981,7 +8039,8 @@
                                 Since it's possible for them to behave in a way
                                 that violates the
 
-                                safety checks we'll disable them until we can add specific checks
+                                safety checks we'll disable them until we can
+                                add specific checks
 
                                 for the HAVING clause
                               footer:
@@ -8042,10 +8101,12 @@
                         This means the prefix will be stable/reliable across
                         runs and make it
 
-                        easier to compare the output generating from different runs
+                        easier to compare the output generating from different
+                        runs
 
 
-                        Update @balena/abstract-sql-compiler from 7.14.1 to 7.17.0
+                        Update @balena/abstract-sql-compiler from 7.14.1 to
+                        7.17.0
 
                         Update @balena/lf-to-abstract-sql from 4.3.0 to 4.4.1
 
@@ -8232,7 +8293,8 @@
                                 This became unnecessary when @balena/sbvr-types
                                 added the concept of
 
-                                cast types since that now specifies how to cast a SERIAL type
+                                cast types since that now specifies how to cast
+                                a SERIAL type
                               footer:
                                 Change-type: patch
                                 change-type: patch
@@ -8397,7 +8459,8 @@
                                 This works on the assumption that it is a rule
                                 query that should always
 
-                                return true and allows ignoring more modification cases where they
+                                return true and allows ignoring more
+                                modification cases where they
 
                                 cannot change the result from true to false
                               footer:
@@ -8611,12 +8674,15 @@
                         'informative'.
 
 
-                        Behaviour change only if type is informative otherwise default 'strict'.
+                        Behaviour change only if type is informative otherwise
+                        default 'strict'.
 
 
-                        An informative reference is just an int field that points
+                        An informative reference is just an int field that
+                        points
 
-                        to another tables id field - like foreign key without constraints
+                        to another tables id field - like foreign key without
+                        constraints
 
                         or foregein key cascades.
                       footer:
@@ -8636,7 +8702,8 @@
                         Since it's possible for them to behave in a way that
                         violates the
 
-                        safety checks we'll disable them until we can add specific checks
+                        safety checks we'll disable them until we can add
+                        specific checks
 
                         for the HAVING clause
                       footer:
@@ -8877,12 +8944,14 @@
                 'informative'.
 
 
-                Behaviour change only if type is informative otherwise default 'strict'.
+                Behaviour change only if type is informative otherwise default
+                'strict'.
 
 
                 An informative reference is just an int field that points
 
-                to another tables id field - like foreign key without constraints
+                to another tables id field - like foreign key without
+                constraints
 
                 or foregein key cascades.
               footer:
@@ -9020,7 +9089,8 @@
                 Since it's possible for them to behave in a way that violates
                 the
 
-                safety checks we'll disable them until we can add specific checks
+                safety checks we'll disable them until we can add specific
+                checks
 
                 for the HAVING clause
               footer:
@@ -9693,7 +9763,8 @@
                         This became unnecessary when @balena/sbvr-types added
                         the concept of
 
-                        cast types since that now specifies how to cast a SERIAL type
+                        cast types since that now specifies how to cast a SERIAL
+                        type
                       footer:
                         Change-type: patch
                         change-type: patch
@@ -9858,7 +9929,8 @@
                         This works on the assumption that it is a rule query
                         that should always
 
-                        return true and allows ignoring more modification cases where they
+                        return true and allows ignoring more modification cases
+                        where they
 
                         cannot change the result from true to false
                       footer:
@@ -10966,7 +11038,8 @@
                 This works on the assumption that it is a rule query that should
                 always
 
-                return true and allows ignoring more modification cases where they
+                return true and allows ignoring more modification cases where
+                they
 
                 cannot change the result from true to false
               footer:
@@ -11786,7 +11859,8 @@
                         This allows specifying the correct type to cast to when
                         necessary
 
-                        rather than relying on the fact the currently all type functions happen
+                        rather than relying on the fact the currently all type
+                        functions happen
 
                         to be integers
                       footer:
@@ -11845,7 +11919,8 @@
                         This allows specifying the correct type to cast to when
                         necessary
 
-                        rather than relying on the fact the currently all type functions happen
+                        rather than relying on the fact the currently all type
+                        functions happen
 
                         to be integers
                       footer:
@@ -11914,7 +11989,8 @@
                                 This allows specifying the correct type to cast
                                 to when necessary
 
-                                rather than relying on the fact the currently all type functions happen
+                                rather than relying on the fact the currently
+                                all type functions happen
 
                                 to be integers
                               footer:
@@ -11995,7 +12071,8 @@
                 This allows specifying the correct type to cast to when
                 necessary
 
-                rather than relying on the fact the currently all type functions happen
+                rather than relying on the fact the currently all type functions
+                happen
 
                 to be integers
               footer:
@@ -14038,7 +14115,8 @@
                                         We do this by using basic scope info to
                                         prune aliased table references
 
-                                        which also allows us to handle aliased select queries in the from
+                                        which also allows us to handle aliased
+                                        select queries in the from
                                       footer:
                                         Change-type: minor
                                         change-type: minor
@@ -14151,7 +14229,8 @@
                                       body: >
                                         Update odata-parser from 1.0.1 to 1.0.3
 
-                                        Update odata-to-abstract-sql from 3.0.0 to 3.0.1
+                                        Update odata-to-abstract-sql from 3.0.0
+                                        to 3.0.1
 
                                         Update sbvr-parser from 0.2.1 to 0.2.2
 
@@ -15324,7 +15403,8 @@
                                 We do this by using basic scope info to prune
                                 aliased table references
 
-                                which also allows us to handle aliased select queries in the from
+                                which also allows us to handle aliased select
+                                queries in the from
                               footer:
                                 Change-type: minor
                                 change-type: minor
@@ -18159,7 +18239,9 @@
 
         ```
 
-        GET /example/application?$select=id,name&$filter=(owns__device/any(d:d/name eq 'test'))&$expand=owns__device($select=id,name)
+        GET
+        /example/application?$select=id,name&$filter=(owns__device/any(d:d/name
+        eq 'test'))&$expand=owns__device($select=id,name)
 
         ```
 
@@ -18261,7 +18343,8 @@
         ```
 
 
-        As one can see we don't apply the device access permission anymore in the select and where subqueries.
+        As one can see we don't apply the device access permission anymore in
+        the select and where subqueries.
       footer:
         Change-type: minor
         change-type: minor
@@ -20008,7 +20091,8 @@
                         We do this by using basic scope info to prune aliased
                         table references
 
-                        which also allows us to handle aliased select queries in the from
+                        which also allows us to handle aliased select queries in
+                        the from
                       footer:
                         Change-type: minor
                         change-type: minor
@@ -20243,7 +20327,8 @@
                 We do this by using basic scope info to prune aliased table
                 references
 
-                which also allows us to handle aliased select queries in the from
+                which also allows us to handle aliased select queries in the
+                from
               footer:
                 Change-type: minor
                 change-type: minor

package/CHANGELOG.md

@@ -5,9 +5,9 @@ automatically by Versionist. DO NOT EDIT THIS FILE MANUALLY!
 This project adheres to [Semantic Versioning](http://semver.org/).
 
 # v16.0.0
-## (2024-03-06)
+## (2024-03-08)
 
-* Update @balena/sbvr-types major [Harald Fischer]
+* Update `@balena/sbvr-types` to enable ISODatestring as internal pine API interface for date and date time fields. [Harald Fischer]
 
 # v15.6.3
 ## (2024-02-29)

package/out/sbvr-api/control-flow.d.ts

@@ -8,7 +8,7 @@ export declare const getMappingFn: (headers?: {
     prefer?: string | string[] | undefined;
 } | undefined) => MappingFunction;
 export declare const delay: (ms: number) => Promise<void>;
-export declare const fromCallback: <T>(resolver: (callback: (err: any, result?: T | undefined) => void) => void) => Promise<T>;
+export declare const fromCallback: <T>(resolver: (callback: (err: any, result?: T) => void) => void) => Promise<T>;
 export declare class TimeoutError extends TypedError {
 }
 export declare const timeout: <T>(promise: Promise<T>, ms: number, msg?: string) => Promise<T>;

package/out/sbvr-api/hooks.d.ts

@@ -63,7 +63,7 @@ declare class Hook<T extends HookFn> {
     constructor(hook: HookBlueprint<T>);
     run(...args: any[]): Promise<void>;
 }
-export declare const rollbackRequestHooks: <T extends InstantiatedHooks>(hooksList: [modelName: string, hooks: T][] | undefined) => void;
+export declare const rollbackRequestHooks: <T extends InstantiatedHooks>(hooksList: Array<[modelName: string, hooks: T]> | undefined) => void;
 export type HookMethod = keyof typeof apiHooks;
 export declare const getHooks: {
     (request: Pick<OptionalField<ParsedODataRequest, 'resourceName'>, 'resourceName' | 'method' | 'vocabulary'>, includeAllVocab: boolean): InstantiatedHooks;

package/out/server-glue/module.d.ts

@@ -17,4 +17,4 @@ export * as webResourceHandler from '../webresource-handler';
 export type { configLoader as ConfigLoader };
 export type { migratorUtils as Migrator };
 declare let envDatabaseOptions: dbModule.DatabaseOptions<string>;
-export declare const init: <T extends string>(app: Express.Application, config?: string | configLoader.Config, databaseOptions?: dbModule.DatabaseOptions<string> | dbModule.DatabaseOptions<T>) => Promise<ReturnType<typeof configLoader.setup>>;
+export declare const init: <T extends string>(app: Express.Application, config?: string | configLoader.Config, databaseOptions?: dbModule.DatabaseOptions<T> | typeof envDatabaseOptions) => Promise<ReturnType<typeof configLoader.setup>>;

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@balena/pinejs",
-  "version": "16.0.0-build-fisehara-update-sbvr-types-cfbbecbb0387e87e17e14be8991be73d1a4efdd0-1",
+  "version": "16.0.0-build-fisehara-update-sbvr-types-f5e8e6ebfd0d3f590ef6ed3fa6b46d1b0861d409-1",
   "main": "out/server-glue/module",
   "type": "commonjs",
   "repository": "git@github.com:balena-io/pinejs.git",
@@ -144,6 +144,6 @@
     "recursive": true
   },
   "versionist": {
-    "publishedAt": "2024-03-06T08:27:30.516Z"
+    "publishedAt": "2024-03-08T13:37:28.583Z"
   }
 }