Hubspot Improvements #12469
Hubspot Improvements #12469
Conversation
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
WalkthroughThe changes across the HubSpot components focus on refactoring and modularizing function calls for better clarity and code organization. Various action modules have been updated to handle parameters as objects, providing more structured inputs. Versions and descriptions in multiple components were incrementally updated, and new test-event files were introduced for testing purposes. Changes
Sequence DiagramsequenceDiagram
participant User
participant HubSpot Component
participant HubSpot API
User ->> HubSpot Component: Trigger Action (e.g., create deal)
HubSpot Component ->> HubSpot API: Send Structured Request
HubSpot API ->> HubSpot Component: Response
HubSpot Component ->> User: Provide Response Data
Assessment Against Linked Issues
Poem
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? TipsChatThere are 3 ways to chat with CodeRabbit:
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)
Additionally, you can add CodeRabbit Configration File (
|
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 10
Outside diff range and nitpick comments (2)
components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1)
Line range hint
97-97: Replace thedeleteoperator with a more performant alternative.- delete params.after; + params.after = undefined;Using
undefinedassignment instead of thedeleteoperator can improve performance by not altering the object's hidden class.components/hubspot/sources/common/common.mjs (1)
Line range hint
85-85: Optimize the use of the 'delete' operator for better performance.The use of the
deleteoperator can lead to performance degradation due to the way JavaScript handles object property deletions. Consider setting the property toundefinedinstead, which avoids the potential deoptimization.- delete params.after; + params.after = undefined;Also applies to: 152-152
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (51)
- components/hubspot/actions/add-contact-to-list/add-contact-to-list.mjs (1 hunks)
- components/hubspot/actions/batch-create-or-update-contact/batch-create-or-update-contact.mjs (1 hunks)
- components/hubspot/actions/common/common-create-object.mjs (3 hunks)
- components/hubspot/actions/common/common-create.mjs (2 hunks)
- components/hubspot/actions/common/common-get-object.mjs (2 hunks)
- components/hubspot/actions/common/common-update-object.mjs (2 hunks)
- components/hubspot/actions/create-associations/create-associations.mjs (2 hunks)
- components/hubspot/actions/create-company/create-company.mjs (1 hunks)
- components/hubspot/actions/create-deal/create-deal.mjs (1 hunks)
- components/hubspot/actions/create-engagement/create-engagement.mjs (1 hunks)
- components/hubspot/actions/create-or-update-contact/create-or-update-contact.mjs (1 hunks)
- components/hubspot/actions/create-ticket/create-ticket.mjs (1 hunks)
- components/hubspot/actions/enroll-contact-into-workflow/enroll-contact-into-workflow.mjs (1 hunks)
- components/hubspot/actions/get-company/get-company.mjs (1 hunks)
- components/hubspot/actions/get-contact/get-contact.mjs (1 hunks)
- components/hubspot/actions/get-deal/get-deal.mjs (1 hunks)
- components/hubspot/actions/get-file-public-url/get-file-public-url.mjs (1 hunks)
- components/hubspot/actions/search-crm/search-crm.mjs (3 hunks)
- components/hubspot/actions/update-company/update-company.mjs (1 hunks)
- components/hubspot/actions/update-contact/update-contact.mjs (1 hunks)
- components/hubspot/common/constants.mjs (2 hunks)
- components/hubspot/hubspot.app.mjs (13 hunks)
- components/hubspot/sources/common/common.mjs (1 hunks)
- components/hubspot/sources/company-updated/company-updated.mjs (2 hunks)
- components/hubspot/sources/contact-updated/contact-updated.mjs (1 hunks)
- components/hubspot/sources/delete-blog-article/delete-blog-article.mjs (2 hunks)
- components/hubspot/sources/line-item-updated/line-item-updated.mjs (2 hunks)
- components/hubspot/sources/new-blog-article/new-blog-article.mjs (2 hunks)
- components/hubspot/sources/new-company-property-change/new-company-property-change.mjs (1 hunks)
- components/hubspot/sources/new-company/new-company.mjs (2 hunks)
- components/hubspot/sources/new-contact-in-list/new-contact-in-list.mjs (2 hunks)
- components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs (1 hunks)
- components/hubspot/sources/new-contact/new-contact.mjs (1 hunks)
- components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (2 hunks)
- components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs (1 hunks)
- components/hubspot/sources/new-deal-updated/new-deal-updated.mjs (2 hunks)
- components/hubspot/sources/new-deal/new-deal.mjs (2 hunks)
- components/hubspot/sources/new-email-event/new-email-event.mjs (2 hunks)
- components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs (2 hunks)
- components/hubspot/sources/new-engagement/new-engagement.mjs (2 hunks)
- components/hubspot/sources/new-event/new-event.mjs (2 hunks)
- components/hubspot/sources/new-form-submission/new-form-submission.mjs (2 hunks)
- components/hubspot/sources/new-line-item/new-line-item.mjs (2 hunks)
- components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs (2 hunks)
- components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs (2 hunks)
- components/hubspot/sources/new-product/new-product.mjs (2 hunks)
- components/hubspot/sources/new-social-media-message/new-social-media-message.mjs (2 hunks)
- components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs (1 hunks)
- components/hubspot/sources/new-ticket/new-ticket.mjs (2 hunks)
- components/hubspot/sources/product-updated/product-updated.mjs (2 hunks)
- components/hubspot/sources/updated-blog-article/updated-blog-article.mjs (2 hunks)
Files skipped from review due to trivial changes (10)
- components/hubspot/actions/batch-create-or-update-contact/batch-create-or-update-contact.mjs
- components/hubspot/actions/create-engagement/create-engagement.mjs
- components/hubspot/actions/create-ticket/create-ticket.mjs
- components/hubspot/actions/enroll-contact-into-workflow/enroll-contact-into-workflow.mjs
- components/hubspot/actions/get-company/get-company.mjs
- components/hubspot/common/constants.mjs
- components/hubspot/sources/new-company-property-change/new-company-property-change.mjs
- components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs
- components/hubspot/sources/new-contact/new-contact.mjs
- components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs
Additional context used
Biome
components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs
[error] 97-97: Avoid the delete operator which can impact performance. (lint/performance/noDelete)
Unsafe fix: Use an undefined assignment instead.
components/hubspot/sources/common/common.mjs
[error] 85-85: Avoid the delete operator which can impact performance. (lint/performance/noDelete)
Unsafe fix: Use an undefined assignment instead.
[error] 152-152: Avoid the delete operator which can impact performance. (lint/performance/noDelete)
Unsafe fix: Use an undefined assignment instead.
Additional comments not posted (57)
components/hubspot/actions/create-deal/create-deal.mjs (3)
1-1: The import path for constants is correctly structured using relative paths.
2-2: The updated import path for the common module aligns with the restructuring mentioned in the PR summary.
Line range hint
3-12: The structure of the exported object is well-defined, with clear metadata and appropriate methods for the action's functionality.components/hubspot/actions/create-company/create-company.mjs (3)
1-1: The import path for constants is correctly structured using relative paths.
2-2: The updated import path for the common module aligns with the restructuring mentioned in the PR summary.
Line range hint
3-12: The structure of the exported object is well-defined, with clear metadata and appropriate methods for the action's functionality.components/hubspot/actions/get-deal/get-deal.mjs (3)
1-1: The import path for constants is correctly structured using relative paths.
2-2: The updated import path for the common module aligns with the restructuring mentioned in the PR summary.
Line range hint
3-15: The structure of the exported object is well-defined, with clear metadata and appropriate methods for the action's functionality.components/hubspot/actions/get-contact/get-contact.mjs (3)
1-1: The import path for constants is correctly structured using relative paths.
2-2: The updated import path for the common module aligns with the restructuring mentioned in the PR summary.
Line range hint
3-15: The structure of the exported object is well-defined, with clear metadata and appropriate methods for the action's functionality.components/hubspot/actions/update-company/update-company.mjs (2)
2-2: Ensure the updated import path aligns with the new directory structure.Verification successful
The import path in
components/hubspot/actions/update-company/update-company.mjscorrectly points to../common/common-update-object.mjs, which aligns with the directory structure as verified.
components/hubspot/actions/update-company/update-company.mjsimports from../common/common-update-object.mjs.- The file
components/hubspot/actions/common/common-update-object.mjsexists at the expected path.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Check if the path to 'common-update-object.mjs' is correctly updated. fd 'common-update-object.mjs' --exec echo {} \;Length of output: 111
Script:
#!/bin/bash # Verify the import statement in update-company.mjs ast-grep --lang javascript --pattern 'import $_ from "../common/common-update-object.mjs";' components/hubspot/actions/update-company/update-company.mjsLength of output: 274
4-4: The version increment to "0.0.7" suggests minor enhancements or fixes. Confirm that this version change is consistent across all related documentation and dependency references.components/hubspot/actions/update-contact/update-contact.mjs (1)
2-2: Verify the import path forcommon-update-object.mjsto ensure it correctly reflects the new file structure.Verification successful
The import path for
common-update-object.mjsincomponents/hubspot/actions/update-contact/update-contact.mjsis correct.
- The file
common-update-object.mjsis located atcomponents/hubspot/actions/common/common-update-object.mjs.- The import statement
import common from "../common/common-update-object.mjs";correctly reflects this path.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Verify the updated import path for 'common-update-object.mjs'. fd 'common-update-object.mjs' --exec echo {} \;Length of output: 111
components/hubspot/actions/create-or-update-contact/create-or-update-contact.mjs (2)
8-8: The description update enhances clarity for API usage. Ensure that this updated description is reflected in all related user-facing documentation.
2-2: Confirm the correctness of the new import path forcommon-create-object.mjswith the updated directory structure.Verification successful
The import path for
common-create-object.mjsincreate-or-update-contact.mjsis correct.
- The discovered file path is
./components/hubspot/actions/common/common-create-object.mjs.- The import statement
import common from "../common/common-create-object.mjs";correctly matches this path.Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Ensure the path to 'common-create-object.mjs' is correctly updated. fd 'common-create-object.mjs' --exec echo {} \;Length of output: 111
components/hubspot/sources/new-blog-article/new-blog-article.mjs (1)
30-33: The parameter structure forgetParamsmethod has been modified to includelimitandcreatedAfter. This is a good improvement for clarity and functionality. Ensure that this change is compatible with all calls togetParamsacross the project.components/hubspot/sources/new-email-event/new-email-event.mjs (1)
32-35: The restructuring of parameters ingetParamsenhances code readability and is consistent with other changes in the codebase. Good job on maintaining consistency.components/hubspot/sources/delete-blog-article/delete-blog-article.mjs (1)
30-34: The updatedgetParamsmethod correctly structures parameters to enhance clarity and maintainability. This change is well-aligned with the overall codebase improvements.components/hubspot/sources/new-line-item/new-line-item.mjs (1)
30-38: Excellent use of structured parameters ingetParams. This approach enhances clarity and ensures that the parameters are explicitly defined, which is crucial for maintainability.components/hubspot/sources/updated-blog-article/updated-blog-article.mjs (1)
34-38: ThegetParamsmethod update is well-implemented, providing clear and structured parameters. This change enhances the readability and maintainability of the code.components/hubspot/sources/new-ticket/new-ticket.mjs (1)
33-41: The refactoring of parameters into a structured object withingetParamsenhances readability and consistency across API calls.components/hubspot/sources/new-company/new-company.mjs (1)
33-41: Well-structured parameter encapsulation ingetParamsmethod, aligning with the overall PR objectives to enhance modularity and readability.components/hubspot/sources/new-product/new-product.mjs (1)
33-41: Consistent improvements in parameter structuring within thegetParamsmethod, enhancing clarity and maintainability.components/hubspot/sources/line-item-updated/line-item-updated.mjs (1)
30-38: The restructuring of parameters ingetParamsmethod is well-executed, promoting consistency and clarity in the codebase.components/hubspot/sources/product-updated/product-updated.mjs (1)
33-41: The restructuring ofgetParamsto include adataobject with sorting options improves readability and standardizes the API call structure. However, ensure that the backend supports these changes, especially the new sorting parameters.components/hubspot/sources/company-updated/company-updated.mjs (1)
33-41: The updatedgetParamsmethod now includes adataobject with sorting parameters, aligning with the changes in other modules. This consistency is beneficial for maintainability. Confirm that thehs_lastmodifieddateproperty is correctly implemented on the backend.Verification successful
The search results show that the
hs_lastmodifieddateproperty is used consistently across multiple files in the codebase, including thecompany-updated.mjsfile. This indicates that the property is recognized and likely supported in the backend, given its widespread usage.
components/hubspot/sources/company-updated/company-updated.mjs:propertyName: "hs_lastmodifieddate"components/hubspot/common/object-types.mjs:"hs_lastmodifieddate"Scripts executed
The following scripts were executed for the analysis:
Script:
#!/bin/bash # Description: Verify backend support for `hs_lastmodifieddate` in `getParams`. # Test: Search for backend handling of `hs_lastmodifieddate`. rg --type mjs $'hs_lastmodifieddate'Length of output: 63
Script:
#!/bin/bash # Description: Verify backend support for `hs_lastmodifieddate` in `getParams`. # Test: Search for backend handling of `hs_lastmodifieddate`. rg --type js 'hs_lastmodifieddate'Length of output: 34
Script:
#!/bin/bash # Description: Verify backend support for `hs_lastmodifieddate` in `getParams`. # Test: Search for backend handling of `hs_lastmodifieddate` across the codebase. rg 'hs_lastmodifieddate'Length of output: 2096
components/hubspot/sources/new-engagement/new-engagement.mjs (1)
35-37: The update to therunmethod introduces a limit of 250 for engagement records retrieval. This change helps manage data volume but ensure it aligns with expected usage patterns and doesn't inadvertently limit necessary data retrieval.components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs (1)
31-33: The update togetParamsnow includes astartTimestampparameter, providing a timestamp context for the email subscriptions timeline. This is a useful addition for time-based queries but verify that this parameter is correctly utilized in subsequent methods.components/hubspot/sources/new-social-media-message/new-social-media-message.mjs (1)
42-45: The restructuring of parameters into an object in thegetParamsmethod enhances readability and maintainability of the code.components/hubspot/actions/add-contact-to-list/add-contact-to-list.mjs (1)
36-44: The restructuring of parameters into an object in therunmethod enhances readability and maintainability. This also aligns well with the PR's objectives of improving parameter handling across the modules.components/hubspot/sources/contact-updated/contact-updated.mjs (1)
42-51: The restructuring of parameters into an object in thegetParamsmethod enhances readability and maintainability of the code. It's clear that this change also aims at making the API calls more explicit and manageable.components/hubspot/actions/common/common-get-object.mjs (1)
23-25: The restructuring of parameters into an object in thegetPropertiesmethod enhances readability and maintainability of the code. This also aligns well with the PR's objectives of improving parameter handling across the modules.components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs (1)
42-50: The restructuring of parameters ingetObjectParamsenhances readability and ensures consistency with other methods. However, ensure that all calls to this method are updated to handle the new structure.components/hubspot/actions/get-file-public-url/get-file-public-url.mjs (1)
38-42: The updated parameter structure forgetSignedUrlis consistent with the overall refactor. It's crucial to verify that thehubspot.getSignedUrlmethod is adapted to accept this new parameter format.components/hubspot/sources/new-form-submission/new-form-submission.mjs (1)
42-44: The introduction of a structured parameter object ingetParamsaligns with the refactoring pattern observed in other components. This should improve the maintainability of the method. Confirm that all dependent methods correctly interpret this new parameter structure.components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs (1)
45-53: The dynamic setting ofpropertyNamebased on the object type ingetObjectParamsis a clever use of conditional logic to handle multiple object types. Ensure that all uses of this method across the codebase are updated to accommodate this change.components/hubspot/actions/common/common-update-object.mjs (2)
13-15: Encapsulation ofobjectTypewithin an object improves readability and maintainability of the code.
50-56: Refactoring of theupdateObjectmethod call to use an object parameter enhances consistency and clarity.components/hubspot/sources/new-contact-in-list/new-contact-in-list.mjs (2)
44-49: Proper encapsulation of parameters in thegetContactmethod call aligns with the PR objectives of improving parameter handling.
58-60: Standardization of parameter structure ingetParamsmethod enhances readability and consistency.components/hubspot/sources/new-deal/new-deal.mjs (1)
57-77: Enhanced parameter structuring ingetParamswith filters and sorting options improves functionality and clarity.components/hubspot/sources/new-event/new-event.mjs (2)
34-37: Encapsulation of parameters in thegetEventsmethod call within thedeployhook aligns with the PR objectives of improving parameter handling.
66-71: Standardization of parameter structure ingetEventParamsmethod enhances readability and consistency.components/hubspot/actions/search-crm/search-crm.mjs (2)
44-46: Ensure thegetPropertiesmethod correctly handles theobjectTypeparameter.This change encapsulates the
objectTypewithin an object, aligning with the new parameter structure. Make sure to validate the entire flow to ensure that theobjectTypeis correctly utilized in other parts of the code.
77-81: Validate the new structure of thesearchCRMmethod call.Ensure that the new parameter structure is correctly handled in all parts of the codebase.
components/hubspot/actions/common/common-create-object.mjs (1)
Line range hint
51-74: Review the error handling in thecreateObjectandupdateObjectmethods.Ensure that the error handling logic is robust and correctly interprets the error messages, especially in cases of object conflicts.
components/hubspot/hubspot.app.mjs (9)
8-8: IntroducedDEFAULT_LIMITconstant to manage default pagination size. This is a good practice for maintainability and consistency across API calls.
43-43: Proper use of destructuring to simplify code ingetPipelinesmethod. This enhances code readability.Also applies to: 44-44
59-59: Good implementation ofgetDealStagesmethod with clear and concise parameter usage. This should improve the clarity of API interactions.Also applies to: 60-60
81-81: SimplifiedlistSchemasmethod by removing unnecessary complexity. This change should make the method easier to understand and maintain.Also applies to: 82-82
119-119: Refactoring ofgetFormsmethod to include pagination. This is a crucial improvement for handling large data sets.Also applies to: 120-123
160-162: RefactoredgetPropertyGroupsmethod to acceptobjectTypeas a parameter. This change is aligned with the overall goal of making parameter passing more explicit and structured.
260-261: RefactoredmakeRequestmethod to use destructuring for cleaner and more readable code. This change also helps in separating pipedream-specific options from other options.Also applies to: 266-266
433-436: Proper use of method overloading ingetLineItemto handle different types of requests by accepting additional options. This flexibility is essential for a robust API.
21-21: Refactored to include pagination support in the options method for lists. Ensure that thepageandlistTypeparameters are properly validated before use to prevent potential issues.Also applies to: 25-27
components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs
Outdated
Show resolved
Hide resolved
components/hubspot/sources/new-deal-updated/new-deal-updated.mjs
Outdated
Show resolved
Hide resolved
components/hubspot/actions/create-or-update-contact/create-or-update-contact.mjs
Show resolved
Hide resolved
components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 0
Outside diff range and nitpick comments (1)
components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1)
Line range hint
97-97: Consider replacing the use of the delete operator with setting the property to undefined for better performance.- delete params.after; + params.after = undefined;
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (43)
- components/hubspot/actions/add-contact-to-list/add-contact-to-list.mjs (2 hunks)
- components/hubspot/actions/create-associations/create-associations.mjs (2 hunks)
- components/hubspot/actions/create-company/create-company.mjs (1 hunks)
- components/hubspot/actions/create-deal/create-deal.mjs (1 hunks)
- components/hubspot/actions/create-engagement/create-engagement.mjs (2 hunks)
- components/hubspot/actions/create-or-update-contact/create-or-update-contact.mjs (1 hunks)
- components/hubspot/actions/create-ticket/create-ticket.mjs (1 hunks)
- components/hubspot/actions/get-company/get-company.mjs (1 hunks)
- components/hubspot/actions/get-contact/get-contact.mjs (1 hunks)
- components/hubspot/actions/get-deal/get-deal.mjs (1 hunks)
- components/hubspot/actions/get-file-public-url/get-file-public-url.mjs (2 hunks)
- components/hubspot/actions/search-crm/search-crm.mjs (4 hunks)
- components/hubspot/actions/update-company/update-company.mjs (1 hunks)
- components/hubspot/actions/update-contact/update-contact.mjs (1 hunks)
- components/hubspot/common/constants.mjs (2 hunks)
- components/hubspot/hubspot.app.mjs (14 hunks)
- components/hubspot/package.json (1 hunks)
- components/hubspot/sources/delete-blog-article/delete-blog-article.mjs (2 hunks)
- components/hubspot/sources/new-contact-in-list/new-contact-in-list.mjs (3 hunks)
- components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (2 hunks)
- components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs (2 hunks)
- components/hubspot/sources/new-email-event/new-email-event.mjs (2 hunks)
- components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs (2 hunks)
- components/hubspot/sources/new-engagement/new-engagement.mjs (2 hunks)
- components/hubspot/sources/new-event/new-event.mjs (3 hunks)
- components/hubspot/sources/new-form-submission/new-form-submission.mjs (3 hunks)
- components/hubspot/sources/new-or-updated-blog-article/new-or-updated-blog-article.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-blog-article/test-event.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-company/new-or-updated-company.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-company/test-event.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-contact/test-event.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs (3 hunks)
- components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs (3 hunks)
- components/hubspot/sources/new-or-updated-deal/new-or-updated-deal.mjs (5 hunks)
- components/hubspot/sources/new-or-updated-deal/test-event.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-line-item/new-or-updated-line-item.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-line-item/test-event.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-product/new-or-updated-product.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-product/test-event.mjs (1 hunks)
- components/hubspot/sources/new-social-media-message/new-social-media-message.mjs (3 hunks)
- components/hubspot/sources/new-ticket/new-ticket.mjs (2 hunks)
- components/hubspot/sources/new-ticket/test-event.mjs (1 hunks)
Files skipped from review due to trivial changes (9)
- components/hubspot/package.json
- components/hubspot/sources/new-contact-in-list/new-contact-in-list.mjs
- components/hubspot/sources/new-or-updated-blog-article/test-event.mjs
- components/hubspot/sources/new-or-updated-company/test-event.mjs
- components/hubspot/sources/new-or-updated-contact/test-event.mjs
- components/hubspot/sources/new-or-updated-deal/test-event.mjs
- components/hubspot/sources/new-or-updated-line-item/test-event.mjs
- components/hubspot/sources/new-or-updated-product/test-event.mjs
- components/hubspot/sources/new-ticket/test-event.mjs
Files skipped from review as they are similar to previous changes (26)
- components/hubspot/actions/add-contact-to-list/add-contact-to-list.mjs
- components/hubspot/actions/create-associations/create-associations.mjs
- components/hubspot/actions/create-company/create-company.mjs
- components/hubspot/actions/create-deal/create-deal.mjs
- components/hubspot/actions/create-engagement/create-engagement.mjs
- components/hubspot/actions/create-or-update-contact/create-or-update-contact.mjs
- components/hubspot/actions/create-ticket/create-ticket.mjs
- components/hubspot/actions/get-company/get-company.mjs
- components/hubspot/actions/get-contact/get-contact.mjs
- components/hubspot/actions/get-deal/get-deal.mjs
- components/hubspot/actions/get-file-public-url/get-file-public-url.mjs
- components/hubspot/actions/search-crm/search-crm.mjs
- components/hubspot/actions/update-company/update-company.mjs
- components/hubspot/actions/update-contact/update-contact.mjs
- components/hubspot/common/constants.mjs
- components/hubspot/sources/delete-blog-article/delete-blog-article.mjs
- components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs
- components/hubspot/sources/new-email-event/new-email-event.mjs
- components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs
- components/hubspot/sources/new-engagement/new-engagement.mjs
- components/hubspot/sources/new-event/new-event.mjs
- components/hubspot/sources/new-form-submission/new-form-submission.mjs
- components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs
- components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs
- components/hubspot/sources/new-social-media-message/new-social-media-message.mjs
- components/hubspot/sources/new-ticket/new-ticket.mjs
Additional context used
Biome
components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs
[error] 97-97: Avoid the delete operator which can impact performance. (lint/performance/noDelete)
Unsafe fix: Use an undefined assignment instead.
Additional comments not posted (8)
components/hubspot/sources/new-or-updated-blog-article/new-or-updated-blog-article.mjs (1)
5-66: The implementation of the new blog article source is well-structured and leverages common components effectively. The use ofcommonmethods and properties ensures consistency across different modules. Adding thenewOnlyproperty with a detailed description enhances user control over the event emission process. The methodsgetTs,generateMeta, andisRelevantare implemented correctly to handle both new and updated blog posts based on thenewOnlyflag. TheprocessResultsmethod properly utilizes pagination and binds context tothis.hubspot.getBlogPosts, which is crucial for correct execution within the async function. Overall, the modifications align with best practices in terms of code reuse and modular design.components/hubspot/sources/new-or-updated-line-item/new-or-updated-line-item.mjs (1)
7-85: This file introduces a new source for handling line items in HubSpot, which is crucial for businesses relying on detailed transaction data. The structure follows the established pattern seen in other HubSpot components, ensuring consistency. ThenewOnlyproperty provides flexibility in event generation, similar to other sources. ThegetTsandgenerateMetamethods are well-implemented, providing necessary timestamps and metadata for events. TheprocessResultsmethod's use ofthis.searchCRMwith the correctly bound context and parameters shows a good understanding of asynchronous JavaScript operations. The inclusion of default and additional properties in thegetParamsmethod is a positive step towards making the component more configurable and useful for different use cases.components/hubspot/sources/new-or-updated-company/new-or-updated-company.mjs (1)
7-88: The new or updated company source component is well-implemented, aligning with the modular and reusable code structure seen in other HubSpot components. ThenewOnlyproperty addition is consistent with other source components, allowing users to filter events based on their needs. Methods such asgetTs,generateMeta, andisRelevantare correctly implemented to handle the logic for new and updated companies. TheprocessResultsmethod effectively utilizesthis.searchCRM, ensuring proper asynchronous behavior and data handling. The use of default and additional properties in thegetParamsmethod enhances the flexibility and utility of the component.
[APROVED]components/hubspot/sources/new-or-updated-product/new-or-updated-product.mjs (1)
7-88: The implementation for handling new or updated products in HubSpot is consistent with the modular approach used across other components. ThenewOnlyproperty is a useful addition, providing users with the ability to tailor event generation to their specific needs. ThegetTs,generateMeta, andisRelevantmethods are implemented effectively, providing the necessary functionality to handle both new and updated products. TheprocessResultsmethod correctly usesthis.searchCRMto handle asynchronous operations and data fetching. The configuration options provided in thegetParamsmethod, including default and additional properties, make this component versatile and adaptable to various use cases.components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (1)
7-88: The refactoring and enhancements in the source component for new or updated contacts in HubSpot are well-integrated and follow the common module pattern effectively. The use of spread operators for props and methods from the common module ensures consistency and maintainability. Additionally, the dynamic generation of property content usingDEFAULT_CONTACT_PROPERTIESis a good use of existing constants to keep the code DRY.components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1)
Line range hint
8-80: The updates to thenew-deal-in-stagesource component, including the version increment and the restructuring of thegetStageParamsmethod, enhance clarity and maintainability. The use of a cleaner structure for thedataobject withingetStageParamsis a significant improvement.The comment on lines 69-80 is still valid and does not need to be repeated.
components/hubspot/sources/new-or-updated-deal/new-or-updated-deal.mjs (1)
Line range hint
9-125: The refactoring in thenew-or-updated-dealsource component is well-executed, with clear and maintainable code structure. The use of constants and common properties/methods enhances the readability and reusability of the code. The handling of new and updated deals through conditional checks ingetTsandgenerateMetamethods is particularly noteworthy for its efficiency.
[APROVED]components/hubspot/hubspot.app.mjs (1)
Line range hint
8-752: The comprehensive updates inhubspot.app.mjsenhance the module's functionality and maintainability significantly. The use of default properties and constants across various methods ensures consistency and reduces errors. The modular structure of the options methods for different properties like deals, contacts, and tickets allows for better scalability and easier updates in the future.The comments on lines 442-444 and 103-105 are still valid and do not need to be repeated.
There was a problem hiding this comment.
Actionable comments posted: 1
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (9)
- components/hubspot/common/constants.mjs (3 hunks)
- components/hubspot/common/object-types.mjs (1 hunks)
- components/hubspot/hubspot.app.mjs (14 hunks)
- components/hubspot/sources/common/common.mjs (3 hunks)
- components/hubspot/sources/new-email-event/new-email-event.mjs (3 hunks)
- components/hubspot/sources/new-email-event/test-event.mjs (1 hunks)
- components/hubspot/sources/new-engagement/new-engagement.mjs (2 hunks)
- components/hubspot/sources/new-or-updated-blog-article/new-or-updated-blog-article.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (1 hunks)
Files skipped from review due to trivial changes (1)
- components/hubspot/sources/new-email-event/test-event.mjs
Files skipped from review as they are similar to previous changes (5)
- components/hubspot/common/constants.mjs
- components/hubspot/hubspot.app.mjs
- components/hubspot/sources/new-email-event/new-email-event.mjs
- components/hubspot/sources/new-engagement/new-engagement.mjs
- components/hubspot/sources/new-or-updated-blog-article/new-or-updated-blog-article.mjs
Additional context used
Biome
components/hubspot/sources/common/common.mjs
[error] 85-85: Avoid the delete operator which can impact performance. (lint/performance/noDelete)
Unsafe fix: Use an undefined assignment instead.
[error] 152-152: Avoid the delete operator which can impact performance. (lint/performance/noDelete)
Unsafe fix: Use an undefined assignment instead.
Additional comments not posted (6)
components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (1)
1-5: Refactored imports and constants for clarity and maintainability.The updated import paths and usage of constants from a centralized location enhance maintainability and ensure consistency across different modules. This aligns with best practices for modular architecture.
components/hubspot/common/object-types.mjs (2)
155-176: Addition of new engagement types.The newly added engagement types (
NOTE,TASK,MEETING,CALL) are clearly defined with appropriate labels and values. This will facilitate easier handling and categorization of different engagement types within the HubSpot ecosystem.
178-219: Addition of new email event types.The comprehensive list of email event types such as
Sent,Dropped,Processed, etc., enhances the granularity with which email events can be tracked and handled. This addition will likely improve the functionality of modules that process or react to email events.components/hubspot/sources/common/common.mjs (3)
32-34: Improved property retrieval with write-only filter.The method
getWriteOnlyPropertiesfetches properties and filters out those that are read-only. This is a crucial enhancement for ensuring that only modifiable properties are processed, which can prevent errors and enforce data integrity.
131-131: Ensure relevance checks are efficiently handled during pagination.The
isRelevantmethod is crucial for determining the relevance of items during pagination. Ensure that this method is optimized to handle large datasets efficiently.
63-66: Optimized event processing and relevance checking in pagination.The methods
processEventsandisRelevantare well-implemented for handling event processing based on relevance and timestamps. However, consider avoiding the use of thedeleteoperator for performance reasons, as it can lead to deoptimization in JavaScript engines.- delete params.after; + params.after = undefined;Also applies to: 85-96
components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs
Outdated
Show resolved
Hide resolved
There was a problem hiding this comment.
Actionable comments posted: 2
Outside diff range and nitpick comments (1)
components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1)
Line range hint
99-99: Consider refactoring to avoid using the delete operator.
Using the delete operator in JavaScript can lead to performance degradation due to changes in the underlying object's shape. Consider setting the property to undefined or restructuring the logic to avoid needing this operation.- delete params.after; + params.after = undefined;
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (34)
- components/hubspot/actions/batch-create-or-update-contact/batch-create-or-update-contact.mjs (2 hunks)
- components/hubspot/actions/common/common-create-object.mjs (4 hunks)
- components/hubspot/actions/common/common-create.mjs (2 hunks)
- components/hubspot/actions/common/common-get-object.mjs (1 hunks)
- components/hubspot/actions/create-deal/create-deal.mjs (1 hunks)
- components/hubspot/actions/create-ticket/create-ticket.mjs (1 hunks)
- components/hubspot/actions/search-crm/search-crm.mjs (4 hunks)
- components/hubspot/hubspot.app.mjs (13 hunks)
- components/hubspot/sources/delete-blog-article/delete-blog-article.mjs (3 hunks)
- components/hubspot/sources/delete-blog-article/test-event.mjs (1 hunks)
- components/hubspot/sources/new-company-property-change/new-company-property-change.mjs (3 hunks)
- components/hubspot/sources/new-company-property-change/test-event.mjs (1 hunks)
- components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs (3 hunks)
- components/hubspot/sources/new-contact-property-change/test-event.mjs (1 hunks)
- components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (3 hunks)
- components/hubspot/sources/new-deal-in-stage/test-event.mjs (1 hunks)
- components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs (3 hunks)
- components/hubspot/sources/new-deal-property-change/test-event.mjs (1 hunks)
- components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs (3 hunks)
- components/hubspot/sources/new-email-subscriptions-timeline/test-event.mjs (1 hunks)
- components/hubspot/sources/new-engagement/new-engagement.mjs (3 hunks)
- components/hubspot/sources/new-engagement/test-event.mjs (1 hunks)
- components/hubspot/sources/new-event/new-event.mjs (4 hunks)
- components/hubspot/sources/new-event/test-event.mjs (1 hunks)
- components/hubspot/sources/new-form-submission/new-form-submission.mjs (4 hunks)
- components/hubspot/sources/new-form-submission/test-event.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs (4 hunks)
- components/hubspot/sources/new-or-updated-crm-object/test-event.mjs (1 hunks)
- components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs (4 hunks)
- components/hubspot/sources/new-or-updated-custom-object/test-event.mjs (1 hunks)
- components/hubspot/sources/new-social-media-message/new-social-media-message.mjs (4 hunks)
- components/hubspot/sources/new-social-media-message/test-event.mjs (1 hunks)
- components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs (3 hunks)
- components/hubspot/sources/new-ticket-property-change/test-event.mjs (1 hunks)
Files skipped from review due to trivial changes (9)
- components/hubspot/sources/delete-blog-article/delete-blog-article.mjs
- components/hubspot/sources/new-deal-in-stage/test-event.mjs
- components/hubspot/sources/new-email-subscriptions-timeline/test-event.mjs
- components/hubspot/sources/new-engagement/test-event.mjs
- components/hubspot/sources/new-event/test-event.mjs
- components/hubspot/sources/new-form-submission/test-event.mjs
- components/hubspot/sources/new-or-updated-crm-object/test-event.mjs
- components/hubspot/sources/new-or-updated-custom-object/test-event.mjs
- components/hubspot/sources/new-ticket-property-change/test-event.mjs
Files skipped from review as they are similar to previous changes (16)
- components/hubspot/actions/batch-create-or-update-contact/batch-create-or-update-contact.mjs
- components/hubspot/actions/common/common-create-object.mjs
- components/hubspot/actions/common/common-create.mjs
- components/hubspot/actions/create-deal/create-deal.mjs
- components/hubspot/actions/create-ticket/create-ticket.mjs
- components/hubspot/hubspot.app.mjs
- components/hubspot/sources/new-company-property-change/new-company-property-change.mjs
- components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs
- components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs
- components/hubspot/sources/new-engagement/new-engagement.mjs
- components/hubspot/sources/new-event/new-event.mjs
- components/hubspot/sources/new-form-submission/new-form-submission.mjs
- components/hubspot/sources/new-or-updated-crm-object/new-or-updated-crm-object.mjs
- components/hubspot/sources/new-or-updated-custom-object/new-or-updated-custom-object.mjs
- components/hubspot/sources/new-social-media-message/new-social-media-message.mjs
- components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs
Additional context used
Biome
components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs
[error] 99-99: Avoid the delete operator which can impact performance. (lint/performance/noDelete)
Unsafe fix: Use an undefined assignment instead.
components/hubspot/actions/common/common-get-object.mjs
[error] 67-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
Unsafe fix: Omit the else clause.
[error] 69-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 71-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 73-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 75-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 77-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
components/hubspot/actions/search-crm/search-crm.mjs
[error] 110-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
Unsafe fix: Omit the else clause.
[error] 112-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 114-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 116-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 118-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 120-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
Additional comments not posted (9)
components/hubspot/sources/new-company-property-change/test-event.mjs (1)
1-23: Test event structure appears correct and comprehensive.components/hubspot/sources/new-deal-property-change/test-event.mjs (1)
1-30: Test event structure is well-formed and suitable for its intended use.components/hubspot/sources/new-contact-property-change/test-event.mjs (1)
1-30: Test event data is correctly structured for contact property changes.components/hubspot/sources/delete-blog-article/test-event.mjs (1)
1-37: Test event structure is comprehensive and well-suited for simulating blog article deletions.components/hubspot/sources/new-email-subscriptions-timeline/new-email-subscriptions-timeline.mjs (1)
Line range hint
1-45: Source component for new email subscriptions is well-implemented and follows good coding practices.components/hubspot/sources/new-social-media-message/test-event.mjs (1)
1-82: Test event file appears correctly structured for its intended use case.
This file provides a comprehensive mock-up of a social media message event, which should be useful for testing the associated module's handling of such events.components/hubspot/sources/new-deal-in-stage/new-deal-in-stage.mjs (1)
1-3: RefactoredgetStageParamsmethod improves clarity and maintainability.
The restructuring into a nested object format using constants likeDEFAULT_LIMITenhances readability and maintainability. The use of constants also helps in managing values centrally, which is a good practice.Also applies to: 10-82
components/hubspot/actions/common/common-get-object.mjs (1)
1-102: Refactored structure enhances clarity and maintainability.
The use of constants for default properties and the structured approach to handling properties improve the readability and maintainability of the code. The async options method is particularly well-implemented, providing clear and concise handling of property options.Tools
Biome
[error] 67-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
Unsafe fix: Omit the else clause.
[error] 69-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 71-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 73-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 75-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 77-79: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
components/hubspot/actions/search-crm/search-crm.mjs (1)
Line range hint
1-170: Enhanced search functionality with optional creation is well-implemented.
The addition of thecreateIfNotFoundoption adds flexibility to the search functionality, allowing for more robust handling of CRM data. The structure of the code is clear, making it easy to understand and maintain.Tools
Biome
[error] 110-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
Unsafe fix: Omit the else clause.
[error] 112-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 114-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 116-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 118-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
[error] 120-122: This else clause can be omitted because previous branches break early. (lint/style/noUselessElse)
There was a problem hiding this comment.
Actionable comments posted: 0
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (7)
- components/hubspot/actions/create-engagement/create-engagement.mjs (3 hunks)
- components/hubspot/common/constants.mjs (3 hunks)
- components/hubspot/hubspot.app.mjs (9 hunks)
- components/hubspot/sources/new-company-property-change/new-company-property-change.mjs (3 hunks)
- components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs (3 hunks)
- components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs (3 hunks)
- components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs (3 hunks)
Files not reviewed due to errors (1)
- components/hubspot/sources/new-company-property-change/new-company-property-change.mjs (no review received)
Files skipped from review as they are similar to previous changes (6)
- components/hubspot/actions/create-engagement/create-engagement.mjs
- components/hubspot/common/constants.mjs
- components/hubspot/hubspot.app.mjs
- components/hubspot/sources/new-contact-property-change/new-contact-property-change.mjs
- components/hubspot/sources/new-deal-property-change/new-deal-property-change.mjs
- components/hubspot/sources/new-ticket-property-change/new-ticket-property-change.mjs
There was a problem hiding this comment.
Actionable comments posted: 3
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (7)
- components/hubspot/actions/common/common-create.mjs (2 hunks)
- components/hubspot/actions/create-engagement/create-engagement.mjs (4 hunks)
- components/hubspot/actions/enroll-contact-into-workflow/enroll-contact-into-workflow.mjs (2 hunks)
- components/hubspot/actions/get-file-public-url/get-file-public-url.mjs (2 hunks)
- components/hubspot/hubspot.app.mjs (9 hunks)
- components/hubspot/sources/new-form-submission/new-form-submission.mjs (4 hunks)
- components/hubspot/sources/new-social-media-message/new-social-media-message.mjs (4 hunks)
Files skipped from review as they are similar to previous changes (6)
- components/hubspot/actions/common/common-create.mjs
- components/hubspot/actions/create-engagement/create-engagement.mjs
- components/hubspot/actions/enroll-contact-into-workflow/enroll-contact-into-workflow.mjs
- components/hubspot/actions/get-file-public-url/get-file-public-url.mjs
- components/hubspot/sources/new-form-submission/new-form-submission.mjs
- components/hubspot/sources/new-social-media-message/new-social-media-message.mjs
Additional comments not posted (3)
components/hubspot/hubspot.app.mjs (3)
8-14: Good use of constants for default values.Defining constants for default properties and limits enhances maintainability and consistency across the module.
49-57: Consider adding error handling in the options method for dealPipeline.Similar to the previous comment, adding try-catch blocks could improve robustness when fetching deal pipelines.
65-73: Consider adding error handling in the options method for stages.Handling potential errors in asynchronous API calls will enhance the reliability of the application.
There was a problem hiding this comment.
Actionable comments posted: 2
Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Files selected for processing (1)
- components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (1 hunks)
Additional comments not posted (2)
components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs (2)
1-5: Review of imports and constants:The imports and constants are well-organized and correctly reference the common functionalities and constants. This structure promotes code reusability and maintainability.
121-121: Review of the sample emit function:The
sampleEmitfunction is correctly placed and serves as a useful tool for developers to understand the expected output format and structure of events. This inclusion supports better testing and integration.
components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs
Show resolved
Hide resolved
components/hubspot/sources/new-or-updated-contact/new-or-updated-contact.mjs
Show resolved
Hide resolved
|
/approve |
Resolves #12449
Resolves #12347
Resolves #12366
Resolves #12365
Summary by CodeRabbit
New Features
Bug Fixes
Refactor
Version Updates