Skip to content

Added ability to define user attributes as callback functions#110

Merged
tg666 merged 1 commit intomainfrom
feature/user-attribute-callback
May 15, 2025
Merged

Added ability to define user attributes as callback functions#110
tg666 merged 1 commit intomainfrom
feature/user-attribute-callback

Conversation

@tg666
Copy link
Contributor

@tg666 tg666 commented May 15, 2025

Summary by CodeRabbit

  • New Features
    • User attributes can now be defined as callback functions, allowing dynamic values to be included during interactions with the Consent Management Platform (CMP).

@tg666 tg666 self-assigned this May 15, 2025
@tg666 tg666 added the enhancement New feature or request label May 15, 2025
@coderabbitai
Copy link

coderabbitai bot commented May 15, 2025

Walkthrough

The changes introduce support for user attributes defined as callback functions in the consent management platform integration. The code now evaluates any function-valued user attributes before including them in API requests, and the changelog has been updated to document this new feature.

Changes

File(s) Change Summary
CHANGELOG.md Updated the "Unreleased" section to document support for user attributes as callback functions.
src/Integration/CmpApiIntegration.mjs Modified preparation of user attributes: function-valued attributes are now evaluated before sending.

Sequence Diagram(s)

sequenceDiagram
    participant User
    participant CmpApiIntegration
    participant ConsentAPI

    User->>CmpApiIntegration: Initiate consent API request with user.attributes
    CmpApiIntegration->>CmpApiIntegration: Iterate over user.attributes
    alt Attribute is a function
        CmpApiIntegration->>CmpApiIntegration: Call function, get value
    else Attribute is not a function
        CmpApiIntegration->>CmpApiIntegration: Use value directly
    end
    CmpApiIntegration->>ConsentAPI: Send request with evaluated attributes
Loading

Poem

In fields of code where attributes grow,
Some are functions, as rabbits now know!
We hop through each, and if it’s a trick,
We call the callback—quick, quick, quick!
The changelog records our clever new feat,
Making consent flows nimble and neat.
🐇✨

Note

⚡️ AI Code Reviews for VS Code, Cursor, Windsurf

CodeRabbit now has a plugin for VS Code, Cursor and Windsurf. This brings AI code reviews directly in the code editor. Each commit is reviewed immediately, finding bugs before the PR is raised. Seamless context handoff to your AI code agent ensures that you can easily incorporate review feedback.
Learn more here.


Note

⚡️ Faster reviews with caching

CodeRabbit now supports caching for code and dependencies, helping speed up reviews. This means quicker feedback, reduced wait times, and a smoother review experience overall. Cached data is encrypted and stored securely. This feature will be automatically enabled for all accounts on May 16th. To opt out, configure Review - Disable Cache at either the organization or repository level. If you prefer to disable all data retention across your organization, simply turn off the Data Retention setting under your Organization Settings.
Enjoy the performance boost—your workflow just got faster.

✨ Finishing Touches
  • 📝 Generate Docstrings

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
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Explain this complex logic.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai explain this code block.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and explain its main purpose.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Support

Need help? Create a ticket on our support page for assistance with any issues or questions.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@tg666 tg666 linked an issue May 15, 2025 that may be closed by this pull request
Copy link

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

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

Actionable comments posted: 0

🧹 Nitpick comments (2)
src/Integration/CmpApiIntegration.mjs (2)

23-29: Consider adding error handling for attribute callbacks.

If a callback function throws an exception, it could cause the entire consent API request to fail silently. Consider adding try/catch handling.

Object.keys(user.attributes).forEach(key => {
    const value = user.attributes[key];
-   attributes[key] = 'function' === typeof value ? value() : value;
+   if ('function' === typeof value) {
+       try {
+           attributes[key] = value();
+       } catch (error) {
+           console.warn(`Error executing callback for attribute "${key}":`, error);
+           attributes[key] = null;
+       }
+   } else {
+       attributes[key] = value;
+   }
});

23-29: Consider passing context to attribute callbacks.

Currently, callbacks are executed without parameters. You might want to consider passing useful context like the current consent state, which would allow for more powerful dynamic attributes.

-Object.keys(user.attributes).forEach(key => {
-    const value = user.attributes[key];
-    attributes[key] = 'function' === typeof value ? value() : value;
-});
+Object.keys(user.attributes).forEach(key => {
+    const value = user.attributes[key];
+    attributes[key] = 'function' === typeof value ? value(userConsent) : value;
+});
📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
Cache: Disabled due to data retention organization setting
Knowledge Base: Disabled due to data retention organization setting

📥 Commits

Reviewing files that changed from the base of the PR and between 89db05e and 681183e.

📒 Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • src/Integration/CmpApiIntegration.mjs (1 hunks)
🧰 Additional context used
🪛 LanguageTool
CHANGELOG.md

[duplication] ~9-~9: Possible typo: you repeated a word.
Context: ...spec/v2.0.0.html). ## [Unreleased] ### Added - Added ability to define user attributes as ca...

(ENGLISH_WORD_REPEAT_RULE)

🔇 Additional comments (3)
CHANGELOG.md (1)

9-10: LGTM - Clear and well-placed changelog entry.

The changelog entry clearly describes the new feature and follows the project's changelog format.

🧰 Tools
🪛 LanguageTool

[duplication] ~9-~9: Possible typo: you repeated a word.
Context: ...spec/v2.0.0.html). ## [Unreleased] ### Added - Added ability to define user attributes as ca...

(ENGLISH_WORD_REPEAT_RULE)

src/Integration/CmpApiIntegration.mjs (2)

23-29: Correctly implements attribute callback processing.

The implementation properly evaluates function attributes before sending them to the API. This allows for dynamic attribute values that can be computed at the time of consent interaction.


36-36: Correctly uses the processed attributes in the request body.

The implementation correctly uses the newly processed attributes object in the request payload.

@tg666 tg666 merged commit 096c18d into main May 15, 2025
2 checks passed
@tg666 tg666 deleted the feature/user-attribute-callback branch May 15, 2025 21:50
@coderabbitai coderabbitai bot mentioned this pull request Jun 16, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Add ability to store user_identity

1 participant