Skip to content

chore: update versions#560

Merged
damonbanks merged 1 commit intomainfrom
changeset-release/main
Jul 10, 2024
Merged

chore: update versions#560
damonbanks merged 1 commit intomainfrom
changeset-release/main

Conversation

@flatfiledocker
Copy link
Contributor

This PR was opened by the Changesets release GitHub action. When you're ready to do a release, you can merge this and the packages will be published to npm automatically. If you're not ready to do a release yet, that's fine, whenever you add more changesets to main, this PR will be updated.

Releases

@flatfile/plugin-delimiter-extractor@2.0.0

Major Changes

  • a6e764b: Removed the 'Required' field check from extractors and the subsequent field.constraints.required.
    This is a breaking change if you are using this required field check in your implementation.

    Source sheets don't require the field.constraints.required.

    If you need to implement this functionality you can use a listener to add in the field.constraints.required to the specific fields you need.

Patch Changes

  • Updated dependencies [a6e764b]
    • @flatfile/util-extractor@2.0.0

@flatfile/plugin-xlsx-extractor@3.0.0

Major Changes

  • a6e764b: Removed the 'Required' field check from extractors and the subsequent field.constraints.required.
    This is a breaking change if you are using this required field check in your implementation.

    Source sheets don't require the field.constraints.required.

    If you need to implement this functionality you can use a listener to add in the field.constraints.required to the specific fields you need.

Patch Changes

  • Updated dependencies [a6e764b]
    • @flatfile/util-extractor@2.0.0

@flatfile/util-extractor@2.0.0

Major Changes

  • a6e764b: Removed the 'Required' field check from extractors and the subsequent field.constraints.required.
    This is a breaking change if you are using this required field check in your implementation.

    Source sheets don't require the field.constraints.required.

    If you need to implement this functionality you can use a listener to add in the field.constraints.required to the specific fields you need.

@flatfile/plugin-json-extractor@0.7.7

Patch Changes

  • Updated dependencies [a6e764b]
    • @flatfile/util-extractor@2.0.0

@flatfile/plugin-xml-extractor@0.5.19

Patch Changes

  • Updated dependencies [a6e764b]
    • @flatfile/util-extractor@2.0.0

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Jul 10, 2024

Walkthrough

In the latest updates to various @flatfile plugins and utilities, the primary change is the removal of the 'Required' field check from extractors and the associated field.constraints.required. This change impacts all plugins relying on this check, necessitating the use of listeners to implement required field constraints. Additionally, dependencies have been updated to @flatfile/util-extractor@2.0.0.

Changes

File Path Change Summary
plugins/delimiter-extractor/CHANGELOG.md Version 2.0.0: Removed 'Required' field check; source sheets no longer need field.constraints.required. Dependency updated to @flatfile/util-extractor@2.0.0.
plugins/json-extractor/CHANGELOG.md Version 0.7.7: Only update is the dependency update to @flatfile/util-extractor@2.0.0.
plugins/xlsx-extractor/CHANGELOG.md Version 3.0.0: Removed 'Required' field check; source sheets no longer need field.constraints.required. Dependency updated to @flatfile/util-extractor@2.0.0.
plugins/xml-extractor/CHANGELOG.md Version 0.5.19: Patch changes including update of dependency to @flatfile/util-extractor@2.0.0.
utils/extractor/CHANGELOG.md Version 2.0.0: Removed 'Required' field check; source sheets no longer need field.constraints.required. Dependency updated to @flatfile/util-extractor@2.0.0.

Sequence Diagram(s)

The changes are not introducing new features or significantly modifying control flows; hence, sequence diagrams are not applicable.

Tip

You can generate walkthrough under a collapsible section

Enable the reviews.collapse_walkthrough setting in your project's settings in CodeRabbit to generate walkthrough in a markdown collapsible section.


Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL

Commits

Files that changed from the base of the PR and between a6e764b and e11da6c.

Files ignored due to path filters (5)
  • plugins/delimiter-extractor/package.json is excluded by !**/*.json
  • plugins/json-extractor/package.json is excluded by !**/*.json
  • plugins/xlsx-extractor/package.json is excluded by !**/*.json
  • plugins/xml-extractor/package.json is excluded by !**/*.json
  • utils/extractor/package.json is excluded by !**/*.json
Files selected for processing (5)
  • plugins/delimiter-extractor/CHANGELOG.md (1 hunks)
  • plugins/json-extractor/CHANGELOG.md (1 hunks)
  • plugins/xlsx-extractor/CHANGELOG.md (1 hunks)
  • plugins/xml-extractor/CHANGELOG.md (1 hunks)
  • utils/extractor/CHANGELOG.md (1 hunks)
Files skipped from review due to trivial changes (3)
  • plugins/json-extractor/CHANGELOG.md
  • plugins/xml-extractor/CHANGELOG.md
  • utils/extractor/CHANGELOG.md
Additional context used
LanguageTool
plugins/delimiter-extractor/CHANGELOG.md

[uncategorized] ~12-~12: Possible missing comma found.
Context: ...uired. If you need to implement this functionality you can use a listener to add in the fi...

(AI_HYDRA_LEO_MISSING_COMMA)

plugins/xlsx-extractor/CHANGELOG.md

[uncategorized] ~12-~12: Possible missing comma found.
Context: ...uired. If you need to implement this functionality you can use a listener to add in the fi...

(AI_HYDRA_LEO_MISSING_COMMA)

Additional comments not posted (2)
plugins/delimiter-extractor/CHANGELOG.md (1)

16-17: LGTM!

The patch changes are straightforward and correct.

plugins/xlsx-extractor/CHANGELOG.md (1)

16-17: LGTM!

The patch changes are straightforward and correct.


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.
    • @coderabbitai help me debug CodeRabbit configuration file.

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 an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @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.

@damonbanks damonbanks merged commit 0072661 into main Jul 10, 2024
@damonbanks damonbanks deleted the changeset-release/main branch July 10, 2024 20:48
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: 0

Outside diff range, codebase verification and nitpick comments (2)
plugins/delimiter-extractor/CHANGELOG.md (1)

12-12: Add missing comma.

A comma is needed after "functionality" for clarity.

-  If you need to implement this functionality you can use a listener to add in the field.constraints.required to the specific fields you need.
+  If you need to implement this functionality, you can use a listener to add in the field.constraints.required to the specific fields you need.
Tools
LanguageTool

[uncategorized] ~12-~12: Possible missing comma found.
Context: ...uired. If you need to implement this functionality you can use a listener to add in the fi...

(AI_HYDRA_LEO_MISSING_COMMA)

plugins/xlsx-extractor/CHANGELOG.md (1)

12-12: Add missing comma.

A comma is needed after "functionality" for clarity.

-  If you need to implement this functionality you can use a listener to add in the field.constraints.required to the specific fields you need.
+  If you need to implement this functionality, you can use a listener to add in the field.constraints.required to the specific fields you need.
Tools
LanguageTool

[uncategorized] ~12-~12: Possible missing comma found.
Context: ...uired. If you need to implement this functionality you can use a listener to add in the fi...

(AI_HYDRA_LEO_MISSING_COMMA)

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.

2 participants