fix: Testing-29th-jan-2nd-commit

[amit429]

Clickup

Please add link here

Code Coverage

Please add code coverage here

UI Preview

Please add screenshots for UI changes

Summary by CodeRabbit

• Chores
  • Added internal logging to improve system observability.

[coderabbitai]

Walkthrough

Aandavan, one line of logging has been added to the sendDeviceToken flow in the org-user service. The constructed payload is now logged before the POST call to /device_token. No control flow changes, no new features—just pure observation of the payload movement through the network.

Changes

Cohort / File(s)	Summary
Logging Enhancement src/app/core/services/org-user.service.ts	Added console logging for the constructed payload before the device token POST request. Single-line addition for observability.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Poem

In the flow of tokens that dance through the night,
A whisper of logs shines spotlight so bright,
One line of truth, before the payload takes flight,
Rajinikanth style—simple, yet right! 🎬✨

🚥 Pre-merge checks | ✅ 1 | ❌ 2

❌ Failed checks (1 warning, 1 inconclusive)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description contains only placeholder text from the template with no actual information filled in about the changes, objectives, or context.	Complete the description by adding relevant Clickup link, code coverage details, and any UI preview if applicable. Provide meaningful context for the logging addition.
Title check	❓ Inconclusive	The title 'fix: Testing-29th-jan-2nd-commit' is vague and non-descriptive, using a date and commit reference instead of clarifying the actual code change.	Replace with a descriptive title that explains the actual change, such as 'fix: add logging for device token payload' or similar to reflect the actual code modification.

✅ Passed checks (1 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch FYLE-testing-4

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Actionable comments posted: 0

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

src/app/core/services/org-user.service.ts (1)

104-112: ⚠️ Potential issue | 🟠 Major

🚫 Don’t log device tokens in plaintext, boss.

Device tokens are sensitive identifiers; logging the raw payload risks leaking PII into logs. Please remove the console log or redact/gate it behind a safe debug logger.

🛠️ Suggested fix

   const payload = {
     data: {
       tokens: [token],
     },
   };
-  console.log('payload', payload);
+  // Avoid logging raw device tokens (PII). If needed, log only metadata.
+  // this.logger.debug('sendDeviceToken payload', { tokenCount: payload.data.tokens.length });

[amit429]

not needed