taTanStack
GitHubformWorkspace
GitHub
  • CI Pipeline Executions
    • Current executionSucceededfix/2337-group-field-boundary
    • Configuration
    • Self-Healing CI
    • Project Graph
    • Resource Usage
    • Analysis
    • Conformance
  • Runs
    • Current runSucceeded
    • Tasks
    • Resource Usage
Insights
  • Compare tasks
  • Analytics
    fix(form-core): restrict form group membership to delimited field paths FormGroupApi.getRelatedFields and the encompassing-group filter in FieldApi.validate select group members with a raw startsWith, so a top-level field named step1Extra counts as a member of the group named step1. Submitting the group marks that field as touched and folds it into areRelatedFieldsValid, and changing it re-runs the group's own validators. Use the existing isFieldInGroup helper, which requires a dot or bracket boundary after the group name, in both places. Fixes #2337
    nx run-many --target=build --exclude=examples/**
Succeeded
Linux
4 CPU cores
read access token used
44f483522338

Get faster results

Learn how to enable distribution.

Atomizer enabled

14 groups of tasks optimized.

Resource usage reports are turned off for this workspace

Your organization has the Resource usage add-on, but this workspace does not collect metrics for non distributed runs. Turn it back on in workspace settings.

© 2026 - Nx Cloud

Terms of ServicePrivacy PolicyChangelogStatusDocsContact Nx CloudPricingCompany@NxDevTools