Skip to content

add built-in field check when doing old metadata migrate #16371

New issue

Have a question about this project? No Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “No 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? No Sign in to your account

Merged
merged 1 commit into from
Mar 20, 2025

Conversation

JohnJyong
Copy link
Collaborator

Summary

add built-in field check when doing old metadata migrate

Tip

Close issue syntax: Fixes #<issue number> or Resolves #<issue number>, see documentation for more details.

fix #16354

Screenshots

Before After
... ...

Checklist

Important

Please review the checklist below before submitting your pull request.

  • This change requires a documentation update, included: Dify Document
  • I understand that this PR may be closed in case there was no previous discussion or issues. (This doesn't apply to typos!)
  • I've added a test for each change that was introduced, and I tried as much as possible to make a single atomic change.
  • I've updated the documentation accordingly.
  • I ran dev/reformat(backend) and cd web && npx lint-staged(frontend) to appease the lint gods

@dosubot dosubot bot added the size:M This PR changes 30-99 lines, ignoring generated files. label Mar 20, 2025
@dosubot dosubot bot added the lgtm This PR has been approved by a maintainer label Mar 20, 2025
@crazywoola crazywoola merged commit 72191f5 into main Mar 20, 2025
9 checks passed
@crazywoola crazywoola deleted the fix/metadata-migrate-command branch March 20, 2025 13:53
parambharat pushed a commit to parambharat/dify that referenced this pull request Mar 31, 2025
No Sign up for free to join this conversation on GitHub. Already have an account? No Sign in to comment
Labels
lgtm This PR has been approved by a maintainer size:M This PR changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

PR change might not work as expected
2 participants