Bump @ngx-formly/core from 6.3.12 to 7.1.0 in /test-app

[dependabot]

Bumps @ngx-formly/core from 6.3.12 to 7.1.0.

Release notes

Sourced from @​ngx-formly/core's releases.

v7.1.0

Highlights

• JSON Schema Conditional Logic (if/then/else) The JSON Schema service matches standard compliance by supporting if, then, and else keywords. This enables defining complex conditional logic directly within schemas for dynamic field configurations.

• CSP-Safe Expression Evaluation Added support for CSP-safe expression evaluation, allowing usages in strict security environments without eval().

  To enable CSP-safe expression evaluation, use the withFormlyFieldExpression configuration helper:

  import { provideFormlyConfig, withFormlyFieldExpression } from '@ngx-formly/core';
  providers: [
  provideFormlyConfig(
  withFormlyFieldExpression()
  ),
  ],

Features

• core: export FormlyFieldConfigPresetProvider via public_api (#4161) (3976e09)
• core: extend formly json schema service to support if/then/else (#4140) (f534999)
• core: support CSP-safe expression evaluation (#4141) (ef839c1)

Bug Fixes

• core: prevent cloning of Promise objects (3238bfb), closes #4159

Special Thanks

• @​jamie-perkins-sp @​agonper

v7.0.1

Bug Fixes

• core: export FormlyTemplate for standalone use (#4149) (6c34e32), closes #4124
• core: merge config when using provideFormlyConfig (#4152) (13ab294), closes #4107 #4111 #4110
• material: remove extra whitespace for hint text (#4150) (4154dae), closes #4106
• optional chain for validity.badInput (#4134) (34e50a9), closes #4131
• preset: clear preset tag after merge (#4151) (2d6f5cd), closes #4110
• primeng: add config options to datepicker (#4143) (#4144) (6cf8f15)

v7.0.0

Highlights

This release add support of standalone components and requires Angular >=18

... (truncated)

Changelog

Sourced from @​ngx-formly/core's changelog.

7.1.0 (2026-01-31)

Features

• core: export FormlyFieldConfigPresetProvider via public_api (#4161) (3976e09)
• core: extend formly json schema service to support if/then/else (#4140) (f534999)
• core: support CSP-safe expression evaluation (#4141) (ef839c1)

Bug Fixes

• core: prevent cloning of Promise objects (3238bfb), closes #4159

7.0.1 (2025-11-16)

Bug Fixes

• core: export FormlyTemplate for standalone use (#4149) (6c34e32), closes #4124
• core: merge config when using provideFormlyConfig (#4152) (13ab294), closes #4107 #4111 #4110
• material: remove extra whitespace for hint text (#4150) (4154dae), closes #4106
• optional chain for validity.badInput (#4134) (34e50a9), closes #4131
• preset: clear preset tag after merge (#4151) (2d6f5cd), closes #4110
• primeng: add config options to datepicker (#4143) (#4144) (6cf8f15)

7.0.0 (2025-06-09)

Features

• ionic: implement ionic labelPlacement prop (#4090) (55cf088), closes #4089

7.0.0-next.0 (2025-05-04)

⚠ BREAKING CHANGES

• core: Deprecated FormlyFormOptions methods has been removed: _markForCheck, _buildForm and _markForCheck.

Features

• core: remove deprecated options methods (#4086) (1cbd47c)

Bug Fixes

• core: clear component refs on FormlyForm destroy (#4085) (06ac47e), closes #4081
• core: non-published preset provider (#4064) (8302480)
• core: overwrite valueChanges without losing pipes when debounce (2ad0ec0)

... (truncated)

Commits

• f2e082c build: enable npm provenance publishing
• e2d4d9d chore(release): 7.1.0
• 3238bfb fix(core): prevent cloning of Promise objects
• 2669218 refactor(core): provide an opt-in for CSP-safe expression configuration
• f534999 feat(core): extend formly json schema service to support if/then/else (#4140)
• ef839c1 feat(core): support CSP-safe expression evaluation (#4141)
• 3976e09 feat(core): export FormlyFieldConfigPresetProvider via public_api (#4161)
• 45f9876 chore(release): 7.0.1
• 13ab294 fix(core): merge config when using provideFormlyConfig (#4152)
• 2d6f5cd fix(preset): clear preset tag after merge (#4151)
• Additional commits viewable in compare view

Maintainer changes

This version was pushed to npm by GitHub Actions, a new releaser for @​ngx-formly/core since your current version.

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)