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

feat: Make entity value_type mandatory with deprecation warning #9

Merged

Conversation

devin-ai-integration[bot]
Copy link

Description

Make it mandatory to specify value_type for an entity to improve type safety and performance.

  • Add deprecation warning when value_type is not specified
  • Add test cases for deprecation warning
  • Prepare for making it mandatory in next release

Fixes feast-dev#4670

Link to Devin run

https://app.devin.ai/sessions/cbcd7e63d76e4aaaa38d747d57b0e9e3

devin-ai-integration bot and others added 2 commits December 11, 2024 03:47
- Add deprecation warning when value_type is not specified for an entity
- Add test cases to verify deprecation warning behavior
- Prepare for making value_type mandatory in next release

Issue: feast-dev#4670

Co-Authored-By: Francisco Javier Arceo <[email protected]>
Signed-off-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
- Reorder imports according to PEP8
- Group standard library imports together
- Fix ruff linting issues

Co-Authored-By: Francisco Javier Arceo <[email protected]>
Signed-off-by: Devin AI <158243242+devin-ai-integration[bot]@users.noreply.github.com>
Copy link
Author

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

  • Address comments on this PR
  • Look at CI failures and help fix them

⚙️ Control Options:

  • Disable automatic comment and CI monitoring

Add "(aside)" to your comment to have me ignore it.

@franciscojavierarceo franciscojavierarceo merged commit 7fd8781 into master Dec 11, 2024
21 checks passed
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.

Make it mandatory to specify value_type for an entity
1 participant