Skip to content

combined-json: fix a confusion with colons in the source path - #674

Merged
xermicus merged 4 commits into
mainfrom
cl/combined-json-colon-path
Oct 8, 2026
Merged

xermicus merged 4 commits into
mainfrom
cl/combined-json-colon-path

Conversation

@xermicus

@xermicus xermicus commented Oct 7, 2026

Copy link
Copy Markdown
Member

Closes #661

@xermicus
xermicus requested review from elle-j and jubnzv October 7, 2026 09:34
Comment thread crates/resolc/src/cli_utils.rs Outdated
}

/// Executes the `resolc` command with the given `arguments` inside the working `directory`.
pub fn execute_resolc_in_directory(arguments: &[&str], directory: &Path) -> CommandResult {

@elle-j elle-j Oct 7, 2026 •

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

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

To resolve a future conflict with PR 678 now, could you update this file's pub fn execute_resolc_in_directory() with 678's crates/resolc/src/cli_utils.rs code? 678's structure is a bit cleaner I think.

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

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

Yeah I agree.

@xermicus
xermicus merged commit 514e7a2 into main Oct 8, 2026
48 of 50 checks passed
@xermicus
xermicus deleted the cl/combined-json-colon-path branch October 8, 2026 16:32
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.

--combined-json with a : in the source path: one contract's code is filed under another contract's name

2 participants