chore(deps): bump @objectstack/objectql from 13.0.0 to 14.3.0

[dependabot]

Bumps @objectstack/objectql from 13.0.0 to 14.3.0.

Release notes

Sourced from @​objectstack/objectql's releases.

@​objectstack/objectql@​14.3.0

Minor Changes

• ff648ad: fix(data): resolve field defaultValues BEFORE the beforeInsert hook (#2703)

  Declarative field defaults (including the current_user token) were resolved by applyFieldDefaults after the user beforeInsert hook ran. A hook that DERIVED one field from another therefore read a stale null for any field that was about to be defaulted — e.g. sales_person: Field.user({ defaultValue: 'current_user' }) left sales_person == null inside the hook, so a derived current_status computed to unassigned unless the client passed the field explicitly.

  applyFieldDefaults now runs at record-initialization time, before beforeInsert, matching the industry-standard order of execution (Salesforce field defaults / ServiceNow dictionary defaults are populated before before- triggers; engine-owned generation — autonumber sequences, encryption, timestamps — stays after the hook). The hook still has final say: it runs after and may override any defaulted field. Defaults still only fill fields left undefined, so client-supplied values are untouched, and the caller's input object is no longer mutated in place.

  Behavior note: a beforeInsert hook can no longer distinguish "client omitted field X" from "field X received its default" for fields that declare a defaultValue — the hook now always sees the resolved default. This matches how Salesforce/ServiceNow behave (before logic sees a fully-initialized record) and is the intended fix.

Patch Changes

• Updated dependencies [2a71f48]
• Updated dependencies [02f6af4]
• Updated dependencies [c1064f1]
  • @​objectstack/spec@​14.3.0
  • @​objectstack/core@​14.3.0
  • @​objectstack/formula@​14.3.0
  • @​objectstack/metadata-core@​14.3.0
  • @​objectstack/metadata-protocol@​14.3.0
  • @​objectstack/types@​14.3.0

Changelog

Sourced from @​objectstack/objectql's changelog.

14.3.0

Minor Changes

• ff648ad: fix(data): resolve field defaultValues BEFORE the beforeInsert hook (#2703)

  Declarative field defaults (including the current_user token) were resolved by applyFieldDefaults after the user beforeInsert hook ran. A hook that DERIVED one field from another therefore read a stale null for any field that was about to be defaulted — e.g. sales_person: Field.user({ defaultValue: 'current_user' }) left sales_person == null inside the hook, so a derived current_status computed to unassigned unless the client passed the field explicitly.

  applyFieldDefaults now runs at record-initialization time, before beforeInsert, matching the industry-standard order of execution (Salesforce field defaults / ServiceNow dictionary defaults are populated before before- triggers; engine-owned generation — autonumber sequences, encryption, timestamps — stays after the hook). The hook still has final say: it runs after and may override any defaulted field. Defaults still only fill fields left undefined, so client-supplied values are untouched, and the caller's input object is no longer mutated in place.

  Behavior note: a beforeInsert hook can no longer distinguish "client omitted field X" from "field X received its default" for fields that declare a defaultValue — the hook now always sees the resolved default. This matches how Salesforce/ServiceNow behave (before logic sees a fully-initialized record) and is the intended fix.

Patch Changes

• Updated dependencies [2a71f48]
• Updated dependencies [02f6af4]
• Updated dependencies [c1064f1]
  • @​objectstack/spec@​14.3.0
  • @​objectstack/core@​14.3.0
  • @​objectstack/formula@​14.3.0
  • @​objectstack/metadata-core@​14.3.0
  • @​objectstack/metadata-protocol@​14.3.0
  • @​objectstack/types@​14.3.0

14.2.0

Patch Changes

• Updated dependencies [ac8f029]
• Updated dependencies [4ab9958]
  • @​objectstack/spec@​14.2.0
  • @​objectstack/core@​14.2.0
  • @​objectstack/formula@​14.2.0

... (truncated)

Commits

• 5a5eba5 chore: version packages (14.3.0) (#2792)
• f517341 chore: version packages (14.2.0) (#2775)
• ff648ad fix(data): resolve field defaultValues before beforeInsert hook (#2703) (#2748)
• 5bdf9a2 chore: version packages (#2768)
• 446a0b8 chore: version packages (#2736)
• 4ea6962 test(objectql): de-flake hook-binder fire-and-forget — ordering assertion ins...
• afa8115 fix(security)!: ADR-0090 follow-ups — driver tenant wall, batch-insert marsha...
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
• @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

[dependabot]

Labels

The following labels could not be found: automated. Please create it before Dependabot can add it to a pull request.

Please fix the above issues or remove invalid values from dependabot.yml.