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

fix(builder): Fix output clash on var steps #1218

Merged
merged 14 commits into from
Aug 6, 2024
Merged

Conversation

Copy link

changeset-bot bot commented Jul 24, 2024

⚠️ No Changeset found

Latest commit: b847354

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

Copy link

nx-cloud bot commented Jul 24, 2024

☁️ Nx Cloud Report

CI is running/has finished running commands for commit b847354. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution


✅ Successfully ran 1 target

Sent with 💌 from NxCloud.

@FuzzB0t FuzzB0t changed the title fix(builder): Allow var step to have duplicate output fix(builder): Fix output clash on var steps Jul 24, 2024
Copy link
Contributor

@dbeal-eth dbeal-eth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this one definitely needs a test to verify this edge case doesn't reappear.

@@ -104,7 104,7 @@ export class ChainDefinition {

for (const output of actionOutputs) {
debug(`deps: ${fullActionName} provides ${output}`);
if (!this.dependencyFor.has(output)) {
if (!this.dependencyFor.has(output) || action == 'setting' || action == 'var') {
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

use triple equals ===. surprised the linter didnt pick this one up.

Copy link
Contributor

@dbeal-eth dbeal-eth left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

also still think we would benefit from specific, purpose built test, not in e2e, that verifies this capability on the definition.ts file.

examples/sample-foundry-project/cannonfile.old.toml Outdated Show resolved Hide resolved
@FuzzB0t FuzzB0t requested a review from dbeal-eth August 2, 2024 16:47
@@ -104,7 104,7 @@ export class ChainDefinition {

for (const output of actionOutputs) {
debug(`deps: ${fullActionName} provides ${output}`);
if (!this.dependencyFor.has(output)) {
if (!this.dependencyFor.has(output) || action === 'setting' || action === 'var') {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This wouldn't work weird when having a var that uses another var? Meaning that it wont be able to find correctly the dependency?

@FuzzB0t FuzzB0t merged commit 2296771 into main Aug 6, 2024
6 of 9 checks passed
@FuzzB0t FuzzB0t deleted the var-description-bug branch August 6, 2024 19:58
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.

3 participants