Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Alex/cos 3288 website not populating on prospects #7298

Merged

Conversation

alexopenline
Copy link
Contributor

@alexopenline alexopenline commented May 24, 2024

Proposed changes

Changes

What types of changes does your code introduce? Put an x in the boxes that apply

  • Bugfix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Code style update (formatting, renaming)
  • Refactoring (no functional changes, no API changes)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • Build related changes
  • Documentation Update (if none of the other choices apply)
  • Other (please describe below)

Additional context

Summary by CodeRabbit

  • Bug Fixes
    • Improved the accuracy of organization updates by modifying parameter handling in the organization event handler.

Copy link
Contributor

coderabbitai bot commented May 24, 2024

Walkthrough

The update involves modifying the parameter of the updateOrganizationFromBrandfetch function within the organization_event_handler.go file. Specifically, the parameter organizationId is replaced with organizationEntity.ID. This change likely aims to improve clarity and consistency in the function's interface.

Changes

File Path Change Summary
.../organization_event_handler.go Modified the updateOrganizationFromBrandfetch function parameter from organizationId to organizationEntity.ID.

Poem

In code's vast and endless sea,
A tweak was made for clarity.
From organizationId to ID we steer,
To make our paths more bright and clear.
With every change, our code does sing,
Hopping forward, like rabbits in spring. 🐇

Tip

New Features and Improvements

Review Settings

Introduced new personality profiles for code reviews. Users can now select between "Chill" and "Assertive" review tones to tailor feedback styles according to their preferences. The "Assertive" profile posts more comments and nitpicks the code more aggressively, while the "Chill" profile is more relaxed and posts fewer comments.

AST-based Instructions

CodeRabbit offers customizing reviews based on the Abstract Syntax Tree (AST) pattern matching. Read more about AST-based instructions in the documentation.

Community-driven AST-based Rules

We are kicking off a community-driven initiative to create and share AST-based rules. Users can now contribute their AST-based rules to detect security vulnerabilities, code smells, and anti-patterns. Please see the ast-grep-essentials repository for more information.

New Static Analysis Tools

We are continually expanding our support for static analysis tools. We have added support for biome, hadolint, and ast-grep. Update the settings in your .coderabbit.yaml file or head over to the settings page to enable or disable the tools you want to use.

Tone Settings

Users can now customize CodeRabbit to review code in the style of their favorite characters or personalities. Here are some of our favorite examples:

  • Mr. T: "You must talk like Mr. T in all your code reviews. I pity the fool who doesn't!"
  • Pirate: "Arr, matey! Ye must talk like a pirate in all yer code reviews. Yarrr!"
  • Snarky: "You must be snarky in all your code reviews. Snark, snark, snark!"

Revamped Settings Page

We have redesigned the settings page for a more intuitive layout, enabling users to find and adjust settings quickly. This change was long overdue; it not only improves the user experience but also allows our development team to add more settings in the future with ease. Going forward, the changes to .coderabbit.yaml will be reflected in the settings page, and vice versa.

Miscellaneous

  • Turn off free summarization: You can switch off free summarization of PRs opened by users not on a paid plan using the enable_free_tier setting.
  • Knowledge-base scope: You can now set the scope of the knowledge base to either the repository (local) or the organization (global) level using the knowledge_base setting. In addition, you can specify Jira project keys and Linear team keys to limit the knowledge base scope for those integrations.
  • High-level summary placement: You can now customize the location of the high-level summary in the PR description using the high_level_summary_placeholder setting (default @coderabbitai summary).
  • Revamped request changes workflow: You can now configure CodeRabbit to auto-approve or request changes on PRs based on the review feedback using the request_changes_workflow setting.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

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>.
    • Generate unit testing code for this file.
    • 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 generate unit testing code for this file.
    • @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 generate interesting stats about this repository and render them as a table.
    • @coderabbitai show all the console.log statements in this repository.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

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 as PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration 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.

@alexopenline alexopenline force-pushed the alex/cos-3288-website-not-populating-on-prospects branch from 783b9c3 to b7459d7 Compare May 25, 2024 05:33
@alexopenline alexopenline marked this pull request as ready for review May 25, 2024 05:33
Copy link
Contributor

@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: 1

Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 60447c6 and b7459d7.
Files selected for processing (1)
  • packages/server/events-processing-platform-subscribers/subscriptions/organization/organization_event_handler.go (5 hunks)
Additional comments not posted (3)
packages/server/events-processing-platform-subscribers/subscriptions/organization/organization_event_handler.go (3)

8-8: Import of neo4jEntity has been added to support the new parameter type in updateOrganizationFromBrandfetch.


474-477: The update to populate the Website field if it is empty aligns with the PR objective to ensure websites are populating on prospects. Good implementation.


376-376: The function updateOrganizationFromBrandfetch now takes an OrganizationEntity instead of an organizationId. Ensure all calls to this function are updated to pass the correct type.

Verification successful

The function updateOrganizationFromBrandfetch now takes an OrganizationEntity instead of an organizationId. All occurrences of this function in the codebase match the new signature, confirming that the function calls have been updated correctly.

  • packages/server/events-processing-platform-subscribers/subscriptions/organization/organization_event_handler.go: h.updateOrganizationFromBrandfetch(ctx, tenant, domain, *organizationEntity, brandfetchResponse)
  • packages/server/events-processing-platform-subscribers/subscriptions/organization/organization_event_handler.go: func (h *organizationEventHandler) updateOrganizationFromBrandfetch(ctx context.Context, tenant, domain string, organizationEntity neo4jEntity.OrganizationEntity, brandfetch BrandfetchResponse) {
  • packages/server/events-processing-platform-subscribers/subscriptions/organization/organization_event_handler.go: span, ctx := opentracing.StartSpanFromContext(ctx, "OrganizationEventHandler.updateOrganizationFromBrandfetch")
Scripts Executed

The following scripts were executed for the analysis:


Script:

#!/bin/bash
# Description: Verify all function calls to `updateOrganizationFromBrandfetch` match the new signature.

# Test: Search for the function usage. Expect: Only occurrences of the new signature.
rg --type go $'updateOrganizationFromBrandfetch'

Length of output: 791

span, ctx := opentracing.StartSpanFromContext(ctx, "OrganizationEventHandler.updateOrganizationFromBrandfetch")
defer span.Finish()

organizationFieldsMask := make([]organizationpb.OrganizationMaskField, 0)
updateGrpcRequest := organizationpb.UpdateOrganizationGrpcRequest{
Tenant: tenant,
OrganizationId: organizationId,
OrganizationId: organizationEntity.ID,
Copy link
Contributor

Choose a reason for hiding this comment

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

The handling of the Employees field in updateOrganizationFromBrandfetch is complex due to different possible data types. Consider simplifying this logic or ensuring robust error handling and validation.

- sEmployees, ok := brandfetch.Company.Employees.(string)
- if ok {
-     if brandfetch.Company.Employees != "" {
-         employees := int64(0)
-         if strings.Contains(sEmployees, "-") {
-             parts := strings.Split(sEmployees, "-")
-             employees, _ = strconv.ParseInt(parts[0], 10, 64)
-         } else {
-             employees, _ = strconv.ParseInt(sEmployees, 10, 64)
-         }
-         if employees > 0 {
-             organizationFieldsMask = append(organizationFieldsMask, organizationpb.OrganizationMaskField_ORGANIZATION_PROPERTY_EMPLOYEES)
-             updateGrpcRequest.Employees = employees
-         }
-     }
- }
+ // Simplify the handling of Employees field by expecting a single format or performing the conversion earlier in the process.

Also applies to: 474-477

Committable suggestion was skipped due low confidence.

@alexopenline alexopenline merged commit 42ed919 into otter May 25, 2024
7 checks passed
@alexopenline alexopenline deleted the alex/cos-3288-website-not-populating-on-prospects branch May 25, 2024 10:05
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.

None yet

2 participants