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

lib: Properly parse ostree tristate #613

Merged
merged 1 commit into from
Mar 11, 2024

Conversation

cgwalters
Copy link
Member

Embarassingly this code hardcoded just one value of the tristate, which caught me out when trying to use it elsewhere.

Closes: #612

Embarassingly this code hardcoded just one value of the tristate,
which caught me out when trying to use it elsewhere.

Closes: ostreedev#612
Copy link
Contributor

@jeckersb jeckersb left a comment

Choose a reason for hiding this comment

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

lgtm


#[test]
fn test_overlayfs_enabled() {
let d0 = indoc::indoc! { r#"
Copy link
Contributor

Choose a reason for hiding this comment

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

I never knew I needed indoc in my life until now

@jeckersb jeckersb merged commit 8d972c1 into ostreedev:main Mar 11, 2024
10 checks passed
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.

Does not properly parse ostree tristates
2 participants