Repository navigation
fix: stop entry.getField printing entry data to the console - #66
Draft
pritesh-jain-cstk wants to merge 1 commit into
Draft
pritesh-jain-cstk wants to merge 1 commit into
pritesh-jain-cstk wants to merge 1 commit into
Conversation
MKT-22140. Remove the leftover debug console.log in the getField path walk. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
🔒 Security Scan Results
⏱️ SLA Breach Summary
✅ BUILD PASSED - All security checks passed |
This was referenced Nov 4, 2026
Draft
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Branch graph
Epic MKT-21682. This PR is highlighted. Only [Routine] depends on [Tests]; the rest are independent.
Merge order: #68 before #69 (#69 is based on #68). #64 and #69 both change
package.jsonandpackage-lock.json: merge #64 first, then bringmasterinto #69 with a merge (no rebase) and regenerate the lock withnpm install --legacy-peer-deps(expect a lock conflict). #65, #66, #67 and #70 are independent.What
Jira: MKT-22140
Consumer impact (runtime, bug fix):
entry.getField()no longer prints the entry's field values to the browser console. Nothing else changes.console.log('mayhem', value)in the getField path walk (since 8689212, in every tag 2.2.1 to 2.2.4, so in the published 2.2.3) prints customer entry content on every call.test/entrySpec.js"getField does not log entry data to the console" spies onconsole.logacross twogetFieldcalls; it fails with the line back.Readiness items
ops.log-hygiene(the code part); Bug MKT-22140Commands (exit codes, Node 24 locally)
npm cinpm ci --legacy-peer-depsnpm run buildlint / typechecknpm testnpm audit --omit=devCommits went through the repo's hooks (GitGuardian pre-commit and pre-push); none bypassed. Local Snyk cannot authenticate (org permission / 401), so the PR's Snyk checks are the scan.
CI:
security-licensefails here as onmaster: it requires the current year inLICENSE(still 2019-2025). Fixed by #64 (DX-29607), not by this PR. All Snyk, GitGuardian, CodeQL and policy checks pass.🤖 Generated with Claude Code