Skip to content

DX | 09-03-2026 | Release#342

Merged
harshithad0703 merged 11 commits intomainfrom
staging
Mar 9, 2026
Merged

DX | 09-03-2026 | Release#342
harshithad0703 merged 11 commits intomainfrom
staging

Conversation

@harshithad0703
Copy link
Contributor

No description provided.

sunil-lakshman and others added 10 commits February 27, 2026 16:27
The previous PR #336 partially fixed asset_fields parameters but used
incorrect field names. This commit corrects all parameter names to match
the CDA API specification.

Changes:
- Changed 'ai_suggested' to 'ai_generated_metadata' in all test files
- Updated SDK documentation to reflect correct parameter names
- All asset_fields tests now pass (verified locally)

Valid asset_fields[] values per API:
- user_defined_fields
- embedded_metadata (not 'embedded')
- ai_generated_metadata (not 'ai_suggested')
- visual_markups

API Error that revealed the issue:
"Invalid values found, supported values are user_defined_fields,
embedded_metadata, ai_generated_metadata, visual_markups"

Files Modified:
- test/api/asset.spec.ts
- test/api/asset-query.spec.ts
- test/api/entry.spec.ts
- test/api/entries.spec.ts
- src/assets/asset.ts (JSDoc)
- src/query/asset-query.ts (JSDoc)
- src/entries/entry.ts (JSDoc)
- src/entries/entries.ts (JSDoc)

Test Results: All 16 asset_fields tests passing (8 API + 8 unit)
…rameter-names

fix: correct asset_fields[] parameter names for DAM 2.0
Problem:
- The test "should compare initial vs delta sync performance" was failing
  intermittently due to network variability
- Assertion expected deltaTime <= initialTime (strict)
- In practice, small syncs (<100ms) have high variance from network latency
- Example failure: initialTime=41ms, deltaTime=74ms (both fast, but failed)

Solution:
- Added hybrid tolerance: max(initialTime * 2, 100ms)
- Allows 2x tolerance OR 100ms absolute threshold (whichever is larger)
- Accounts for network variability while catching real performance regressions

Impact:
- Makes test more resilient to network conditions
- Still catches meaningful performance degradation
- Prevents false negatives from minor timing fluctuations
…ion-tolerance

fix: add network tolerance to sync performance assertion
fix: added support for special symbols in regex and added tpe support…
@harshithad0703 harshithad0703 requested a review from a team as a code owner March 9, 2026 06:06
@github-actions
Copy link

github-actions bot commented Mar 9, 2026

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 1 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 1
  • Medium without fixes: 0
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@github-actions
Copy link

github-actions bot commented Mar 9, 2026

Coverage report

St.
Category Percentage Covered / Total
🟢 Statements 99.32% 877/883
🟢 Branches 97.23% 281/289
🟢 Functions 97.95% 191/195
🟢 Lines 99.4% 832/837

Test suite run success

654 tests passing in 31 suites.

Report generated by 🧪jest coverage report action from 7d2b228

@github-actions
Copy link

github-actions bot commented Mar 9, 2026

🔒 Security Scan Results

ℹ️ Note: Only vulnerabilities with available fixes (upgrades or patches) are counted toward thresholds.

Check Type Count (with fixes) Without fixes Threshold Result
🔴 Critical Severity 0 0 10 ✅ Passed
🟠 High Severity 0 1 25 ✅ Passed
🟡 Medium Severity 0 0 500 ✅ Passed
🔵 Low Severity 0 0 1000 ✅ Passed

⏱️ SLA Breach Summary

✅ No SLA breaches detected. All vulnerabilities are within acceptable time thresholds.

Severity Breaches (with fixes) Breaches (no fixes) SLA Threshold (with/no fixes) Status
🔴 Critical 0 0 15 / 30 days ✅ Passed
🟠 High 0 0 30 / 120 days ✅ Passed
🟡 Medium 0 0 90 / 365 days ✅ Passed
🔵 Low 0 0 180 / 365 days ✅ Passed

ℹ️ Vulnerabilities Without Available Fixes (Informational Only)

The following vulnerabilities were detected but do not have fixes available (no upgrade or patch). These are excluded from failure thresholds:

  • Critical without fixes: 0
  • High without fixes: 1
  • Medium without fixes: 0
  • Low without fixes: 0

✅ BUILD PASSED - All security checks passed

@harshithad0703 harshithad0703 merged commit a763410 into main Mar 9, 2026
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

6 participants