-
Notifications
You must be signed in to change notification settings - Fork 83
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
chore(release): pull main into develop post release v3.3.0 #1668
Conversation
WalkthroughThe recent updates across various packages primarily focus on enhancing the Changes
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 (
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #1668 +/- ##
===========================================
+ Coverage 53.89% 53.90% +0.01%
===========================================
Files 461 461
Lines 15588 15611 +23
Branches 3095 3102 +7
===========================================
+ Hits 8401 8415 +14
- Misses 5871 5890 +19
+ Partials 1316 1306 -10 ☔ View full report in Codecov by Sentry. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 1
Configuration used: CodeRabbit UI
Files ignored due to path filters (15)
package-lock.json
is excluded by:!**/*.json
package.json
is excluded by:!**/*.json
packages/analytics-js-common/package.json
is excluded by:!**/*.json
packages/analytics-js-common/project.json
is excluded by:!**/*.json
packages/analytics-js-integrations/package.json
is excluded by:!**/*.json
packages/analytics-js-integrations/project.json
is excluded by:!**/*.json
packages/analytics-js-plugins/package.json
is excluded by:!**/*.json
packages/analytics-js-plugins/project.json
is excluded by:!**/*.json
packages/analytics-js/package.json
is excluded by:!**/*.json
packages/analytics-js/project.json
is excluded by:!**/*.json
packages/analytics-v1.1/package.json
is excluded by:!**/*.json
packages/analytics-v1.1/project.json
is excluded by:!**/*.json
packages/loading-scripts/package.json
is excluded by:!**/*.json
packages/loading-scripts/project.json
is excluded by:!**/*.json
packages/sanity-suite/package.json
is excluded by:!**/*.json
Files selected for processing (14)
- packages/analytics-js-common/CHANGELOG.md (1 hunks)
- packages/analytics-js-common/CHANGELOG_LATEST.md (1 hunks)
- packages/analytics-js-integrations/CHANGELOG.md (1 hunks)
- packages/analytics-js-integrations/CHANGELOG_LATEST.md (1 hunks)
- packages/analytics-js-plugins/CHANGELOG.md (1 hunks)
- packages/analytics-js-plugins/CHANGELOG_LATEST.md (1 hunks)
- packages/analytics-js/CHANGELOG.md (1 hunks)
- packages/analytics-js/CHANGELOG_LATEST.md (1 hunks)
- packages/analytics-v1.1/CHANGELOG.md (1 hunks)
- packages/analytics-v1.1/CHANGELOG_LATEST.md (1 hunks)
- packages/loading-scripts/CHANGELOG.md (1 hunks)
- packages/loading-scripts/CHANGELOG_LATEST.md (1 hunks)
- packages/sanity-suite/CHANGELOG.md (1 hunks)
- sonar-project.properties (1 hunks)
Files skipped from review due to trivial changes (5)
- packages/analytics-js-integrations/CHANGELOG_LATEST.md
- packages/analytics-js-plugins/CHANGELOG.md
- packages/analytics-v1.1/CHANGELOG.md
- packages/sanity-suite/CHANGELOG.md
- sonar-project.properties
Additional comments: 10
packages/analytics-v1.1/CHANGELOG_LATEST.md (1)
- 1-10: LGTM! The changelog is clear and follows the conventional format, providing transparency and traceability for the changes.
packages/analytics-js-plugins/CHANGELOG_LATEST.md (1)
- 1-10: LGTM! The changelog is well-structured, providing clear information on dependency updates and bug fixes.
packages/loading-scripts/CHANGELOG_LATEST.md (1)
- 1-11: LGTM! The changelog provides a clear and structured overview of the updates, including dependency updates and bug fixes.
packages/analytics-js-common/CHANGELOG_LATEST.md (1)
- 1-12: LGTM! The changelog is comprehensive, detailing new features and bug fixes in a clear and structured manner.
packages/analytics-js/CHANGELOG_LATEST.md (1)
- 1-13: LGTM! The changelog provides a clear and structured overview of the updates, including dependency updates and bug fixes.
packages/loading-scripts/CHANGELOG.md (1)
- 5-15: LGTM! The comprehensive changelog provides a clear historical view of the changes across versions, maintaining consistency and traceability.
packages/analytics-js-common/CHANGELOG.md (1)
- 10-10: Consider revising "apiobject" and "apioptions" to ensure they are correctly spelled or formatted according to your project's naming conventions. If these are specific technical terms within your project, consider using backticks (
apiobject
andapioptions
) for clarity.packages/analytics-js-integrations/CHANGELOG.md (1)
- 5-9: The documentation of the dependency update for
@rudderstack/analytics-js-common
to version 3.0.1 in version 3.0.2 is clear and accurate.packages/analytics-js/CHANGELOG.md (2)
- 5-10: The version update and dependency updates are correctly documented.
- 12-16: The bug fixes section is well-documented, providing clear traceability to the issues and commits.
|
||
### Bug Fixes | ||
|
||
* optimize localstorage transactions ([#1651](https://github.com/rudderlabs/rudder-sdk-js/issues/1651)) ([1289217](https://github.com/rudderlabs/rudder-sdk-js/commit/12892176578dd3628fded2311ea2548e3ff5802c)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The term "localstorage" might be more accurately written as "localStorage" to reflect the correct API name in web development. Consider updating this for clarity and consistency with web standards.
- * optimize localstorage transactions ([#1651](https://github.com/rudderlabs/rudder-sdk-js/issues/1651)) ([1289217](https://github.com/rudderlabs/rudder-sdk-js/commit/12892176578dd3628fded2311ea2548e3ff5802c))
+ * optimize localStorage transactions ([#1651](https://github.com/rudderlabs/rudder-sdk-js/issues/1651)) ([1289217](https://github.com/rudderlabs/rudder-sdk-js/commit/12892176578dd3628fded2311ea2548e3ff5802c))
Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation.
* optimize localstorage transactions ([#1651](https://github.com/rudderlabs/rudder-sdk-js/issues/1651)) ([1289217](https://github.com/rudderlabs/rudder-sdk-js/commit/12892176578dd3628fded2311ea2548e3ff5802c)) | |
* optimize localStorage transactions ([#1651](https://github.com/rudderlabs/rudder-sdk-js/issues/1651)) ([1289217](https://github.com/rudderlabs/rudder-sdk-js/commit/12892176578dd3628fded2311ea2548e3ff5802c)) |
size-limit report 📦
|
…#1669) fix: add backward compatibility for storage api
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Review Status
Actionable comments generated: 2
Configuration used: CodeRabbit UI
Files ignored due to path filters (9)
package-lock.json
is excluded by:!**/*.json
package.json
is excluded by:!**/*.json
packages/analytics-js-plugins/package.json
is excluded by:!**/*.json
packages/analytics-js-plugins/project.json
is excluded by:!**/*.json
packages/analytics-js/package.json
is excluded by:!**/*.json
packages/analytics-js/project.json
is excluded by:!**/*.json
packages/loading-scripts/package.json
is excluded by:!**/*.json
packages/loading-scripts/project.json
is excluded by:!**/*.json
packages/sanity-suite/package.json
is excluded by:!**/*.json
Files selected for processing (9)
- packages/analytics-js-plugins/CHANGELOG.md (1 hunks)
- packages/analytics-js-plugins/CHANGELOG_LATEST.md (1 hunks)
- packages/analytics-js-plugins/src/utilities/retryQueue/RetryQueue.ts (2 hunks)
- packages/analytics-js/CHANGELOG.md (1 hunks)
- packages/analytics-js/CHANGELOG_LATEST.md (1 hunks)
- packages/loading-scripts/CHANGELOG.md (1 hunks)
- packages/loading-scripts/CHANGELOG_LATEST.md (1 hunks)
- packages/sanity-suite/CHANGELOG.md (1 hunks)
- sonar-project.properties (1 hunks)
Files skipped from review as they are similar to previous changes (5)
- packages/analytics-js/CHANGELOG_LATEST.md
- packages/loading-scripts/CHANGELOG.md
- packages/loading-scripts/CHANGELOG_LATEST.md
- packages/sanity-suite/CHANGELOG.md
- sonar-project.properties
Additional comments: 7
packages/analytics-js-plugins/CHANGELOG_LATEST.md (1)
- 1-7: The change log update for version
3.0.3
ofanalytics-js-plugins
is clear and adheres to standard practices, detailing the bug fixes for backward compatibility with the storage API effectively.packages/analytics-js-plugins/CHANGELOG.md (1)
- 5-11: The changelog entry for version 3.0.3 of
@rudderstack/analytics-js-plugins
clearly documents the addition of backward compatibility for the storage API. This is a crucial update for users relying on previous storage API versions. It's important to ensure that all relevant details about such changes are captured in the changelog to aid developers in understanding the impact of the update on their implementations.packages/analytics-js-plugins/src/utilities/retryQueue/RetryQueue.ts (2)
- 8-8: The import statement correctly includes
isDefined
,isFunction
, andisNullOrUndefined
from@rudderstack/analytics-js-common/utilities/checks
. This aligns with the summary stating thatisDefined
andisNullOrUndefined
functions are replaced withisDefined
,isFunction
, andisNullOrUndefined
.- 708-721: The addition of a check for the existence of the
keys
function in the storage engine (lines 708-721) is a good practice for ensuring backward compatibility. This change allows theRetryQueue
class to work with different versions of the storage engine that may or may not support thekeys
method. However, it's important to ensure that thestorageEngine
object always has alength
property and akey
method when thekeys
method is not available. This assumption should be verified if not already known to be true.packages/analytics-js/CHANGELOG.md (3)
- 5-5: The markdown link for version
3.0.3
seems to be formatted correctly, but static analysis hinted at possible unpaired symbols. This appears to be a false positive, as the markdown syntax for links is correct throughout the document. No action is required here.- 5-5: Ensure the correctness of GitHub comparison links for each version. While the format looks correct, it's important to manually verify that these links lead to the intended comparisons between versions.
- 7-7: The descriptions for features and bug fixes are clear and concise, providing valuable context for users. Including links to relevant GitHub issues and commits is a good practice for transparency.
Quality Gate passedIssues Measures |
PR Description
Please include a summary of the change along with the relevant motivation and context.
Linear task (optional)
Linear task link
Cross Browser Tests
Please confirm you have tested for the following browsers:
Sanity Suite
Security
Summary by CodeRabbit