Skip to content

Allow partial parsing when default target and profile names are used#12498

Merged
ash2shukla merged 2 commits intomainfrom
ash2shukla/fix/enable-partial-parse-for-default-target
Feb 19, 2026
Merged

Allow partial parsing when default target and profile names are used#12498
ash2shukla merged 2 commits intomainfrom
ash2shukla/fix/enable-partial-parse-for-default-target

Conversation

@ash2shukla
Copy link
Contributor

Resolves #7612

Problem

If default target and profile names are passed explicitly then the vars hash doesn't get computed correctly as when its not passed explicitly we currently treat profile_name and target_name as empty strings instead of actual resolved names.

Solution

Use resolved profile and target names from config

Checklist

  • I have read the contributing guide and understand what's expected of me.
  • I have run this code in development, and it appears to resolve the stated issue.
  • This PR includes tests, or tests are not required or relevant for this PR.
  • This PR has no interface changes (e.g., macros, CLI, logs, JSON artifacts, config files, adapter interface, etc.) or this PR has already received feedback and approval from Product or DX.
  • This PR includes type annotations for new and modified functions.

@ash2shukla ash2shukla requested a review from a team as a code owner February 16, 2026 17:51
@cla-bot cla-bot bot added the cla:yes label Feb 16, 2026
@codecov
Copy link

codecov bot commented Feb 16, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 91.38%. Comparing base (9cf32c8) to head (cb57eba).
⚠️ Report is 5 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main   #12498      +/-   ##
==========================================
- Coverage   91.39%   91.38%   -0.01%     
==========================================
  Files         203      203              
  Lines       25445    25445              
==========================================
- Hits        23256    23254       -2     
- Misses       2189     2191       +2     
Flag Coverage Δ
integration 88.25% <ø> (-0.02%) ⬇️
unit 65.10% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Components Coverage Δ
Unit Tests 65.10% <ø> (ø)
Integration Tests 88.25% <ø> (-0.02%) ⬇️
🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

@ash2shukla ash2shukla self-assigned this Feb 16, 2026
Copy link
Contributor

@MichelleArk MichelleArk left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🔥

@ash2shukla ash2shukla merged commit 0168c62 into main Feb 19, 2026
123 checks passed
@ash2shukla ash2shukla deleted the ash2shukla/fix/enable-partial-parse-for-default-target branch February 19, 2026 04:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[CT-2572] [Feature] Enable partial parsing when --target is the same as the default target in profiles.yml

2 participants

Comments