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

🔖 release v1.0.9 #13

Merged
merged 1 commit into from
Apr 27, 2024
Merged

🔖 release v1.0.9 #13

merged 1 commit into from
Apr 27, 2024

Conversation

techouse
Copy link
Owner

@techouse techouse commented Apr 27, 2024

1.0.9

Summary by CodeRabbit

  • Bug Fixes

    • Resolved an issue with incorrect parsing of nested parameters in property names.
  • Chores

    • Updated the library version and test dependency to enhance performance and compatibility.

## 1.0.9

- [FIX] incorrect parsing of nested params with closing square bracket `]` in the property name (#12)
@techouse techouse added the release release label Apr 27, 2024
@techouse techouse self-assigned this Apr 27, 2024
Copy link

coderabbitai bot commented Apr 27, 2024

Walkthrough

This update primarily focuses on fixing a bug related to the parsing of nested parameters in the qs_dart library and updating dependencies. The version has been incremented to ensure compatibility and improve functionality.

Changes

File Summary of Changes
CHANGELOG.md Fixed incorrect parsing of nested parameters with ] in names.
pubspec.yaml Updated version and test dependency.

🐰✨
In the fields of code, where the curly braces play,
A small version bump comes with the day.
Nested brackets, once lost, now found,
With tests updated, we stand our ground.
Hoppity-hop, the bugs we sweep away! 🌟🐾


Recent Review Details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits Files that changed from the base of the PR and between 6a6a3df and e0d46a2.
Files selected for processing (2)
  • CHANGELOG.md (1 hunks)
  • pubspec.yaml (2 hunks)
Files skipped from review due to trivial changes (1)
  • pubspec.yaml
Additional Context Used
LanguageTool (13)
CHANGELOG.md (13)

Near line 3: Possible spelling mistake found.
Context: ....9 - [FIX] incorrect parsing of nested params with closing square bracket ] in the ...


Near line 3: Unpaired symbol: ‘[’ seems to be missing
Context: ...sted params with closing square bracket ] in the property name ([#12](https://gi...


Near line 12: Possible spelling mistake found.
Context: ...] add comparison test between output of qs_dart and [qs](https://www.npmjs.com/pac...


Near line 12: Unpaired symbol: ‘]’ seems to be missing
Context: ...ison test between output of qs_dart and qs - ...


Near line 12: Possible spelling mistake found.
Context: ...son test between output of qs_dart and qs - [C...


Near line 22: Possible spelling mistake found.
Context: ...ed in v1.0.7 ## 1.0.7 - [FIX] disable DecodeOptions.decodeDotInKeys by default to restore ...


Near line 22: Possible spelling mistake. ‘behavior’ is American English.
Context: ...tInKeys` by default to restore previous behavior - [FIX] optimize encoding performance u...


Near line 27: An accent character was used instead of an apostrophe.
Context: ...age ## 1.0.6 - [FEAT] add support for Sets - [CHORE] rename `_encode.allowEmptyArr...


Near line 28: Possible spelling mistake found.
Context: ...add support for Sets - [CHORE] rename _encode.allowEmptyArrays to _encode.allowEmptyLists - [CHORE]...


Near line 29: Possible spelling mistake found.
Context: ...ode.allowEmptyLists- [CHORE] optimizeUtils.removeUndefinedFromListmethod - [CHORE] delete dead code in...


Near line 44: Possible spelling mistake found.
Context: ... and Undefined ## 1.0.3 - [FIX] fix Utils.isNonNullishPrimitive method to enable encoding Enums ## 1....


Near line 48: Possible spelling mistake found.
Context: ... encoding Enums ## 1.0.2 - [FEAT] add equatability to Undefined - [CHORE] add more tests t...


Near line 68: Possible spelling mistake found.
Context: ...ion ## 1.0.0+1 - [FIX] fix repository url in pubspec.yaml ## 1.0.0 - Initial re...

Additional comments not posted (1)
CHANGELOG.md (1)

3-3: The entry for the bug fix in version 1.0.9 is clearly documented. The markdown syntax for the link is correctly used, and the description is technically accurate.


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.

@techouse techouse changed the title 🔖 release/v1.0.9 🔖 release v1.0.9 Apr 27, 2024
Copy link

codecov bot commented Apr 27, 2024

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 98.08%. Comparing base (6a6a3df) to head (e0d46a2).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #13   +/-   ##
=======================================
  Coverage   98.08%   98.08%           
=======================================
  Files          13       13           
  Lines         625      625           
=======================================
  Hits          613      613           
  Misses         12       12           

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@techouse techouse merged commit c85c8a0 into main Apr 27, 2024
6 checks passed
@techouse techouse deleted the release/v1.0.9 branch April 27, 2024 19:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
release release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant