docs: Clarify Quick Start: fitness_functions.yaml vs config.py#8
Draft
tjirab wants to merge 2 commits into
Draft
docs: Clarify Quick Start: fitness_functions.yaml vs config.py#8tjirab wants to merge 2 commits into
tjirab wants to merge 2 commits into
Conversation
Quick start previously implied config.py holds configuration; make clear that YAML is the editable FF config and project config.py is optional SQLMesh loader wiring for native sqlmesh commands. Co-authored-by: Cursor <cursoragent@cursor.com>
tjirab
changed the title
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
1 participant
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.
Summary
fitness_functions.yamlis where users put fitness function settings (thresholds, rule toggles, etc.)config.pyas optional SQLMesh loader wiring, needed only for native SQLMesh commands (sqlmesh plan, etc.), not forsqlmesh-ff lintconfig.pyTest plan
Made with Cursor