[components] project_name -> code_location_name in scaffolded pyproject.toml #27480
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 & Motivation
The
tool.dagster
section in our scaffoldedpyproject.toml
contained aproject_name
field. However, this isn't actually read by our tooling. What is read is acode_location_name
field. This renames theproject_name
field tocode_location_name
. It affects bothdagster
anddagster-dg
(which had started by copying thepyproject.toml
scaffolding from dagster core).How I Tested These Changes
Tweaked unit tests.