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

Add missing manifest_path field to Artifact #195

Merged
merged 4 commits into from Jul 4, 2022
Merged

Conversation

morr0ne
Copy link
Contributor

@morr0ne morr0ne commented Jul 2, 2022

Fixes #187

@morr0ne
Copy link
Contributor Author

morr0ne commented Jul 2, 2022

I did overlook that the test samples need to be fixed

@morr0ne
Copy link
Contributor Author

morr0ne commented Jul 2, 2022

Okay so apperantaly parse_stream_is_robust is failing but I'm not sure why.

@morr0ne
Copy link
Contributor Author

morr0ne commented Jul 2, 2022

Nevermind I figure it out, I also added the proper entry to the changelog.

src/messages.rs Outdated
@@ -34,6 +34,8 @@ pub struct ArtifactProfile {
pub struct Artifact {
/// The package this artifact belongs to
pub package_id: PackageId,
/// Path containing the `Cargo.toml`
Copy link
Owner

Choose a reason for hiding this comment

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

I think it's the path to the Cargo.toml. the current doc comment sounds like it would point to the parent folder

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah good catch, I'll fix it.

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.

Why isn't manifest_path made available?
2 participants