chore(main): release json-viewer 3.2.3 #421
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
✅ Deploy Preview for any-viewer ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Removed dependencies detected. Learn more about Socket for GitHub ↗︎ 🚮 Removed packages: @textea/[email protected] |
pionxzh
deleted the
release-please--branches--main--components--json-viewer
branch
|
🤖 Release is at https://github.com/TexteaInc/json-viewer/releases/tag/json-viewer-v3.2.3 🌻 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
🤖 I have created a release beep boop
3.2.3 (2023-11-04)
Bug Fixes
Note: This fix introduced
nestedIndextoDataItemProps. It shouldn't break existing things. But if you are extending theObjecttype, which will receive Array as input, please adopt the same strategy we do in this PR to calculate the key correctly.This PR was generated with Release Please. See documentation.