Support for the full static sources - #10
Merged
Merged
Conversation
This file contains hidden or 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
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.
This pull request introduces improvements to the documentation and validation logic for defining data sources in the project. The main focus is on clarifying how to define sources with static attributes and ensuring that such sources are correctly validated. The changes enhance user guidance and add safeguards to prevent misconfiguration.
Documentation improvements:
SourceCollection, including explicit instructions and code samples for sources with only static attributes. [1] [2] [3]Validation enhancements:
SourceConfiginconfig.pyto ensure that if a source has no temporal columns (i.e., is static), all feature columns must be marked withstatic=True, raising a helpful error otherwise.Versioning:
0.1.9to0.1.10inpyproject.tomlto reflect these changes.