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

test: Run toml-test #111

Merged
merged 1 commit into from
Aug 21, 2021
Merged

test: Run toml-test #111

merged 1 commit into from
Aug 21, 2021

Conversation

epage
Copy link
Member

@epage epage commented Aug 16, 2021

We are skipping all tests that toml_edit fails with the expectation
that we'll use the ignores as the task list for what is left towards
toml 1.0 and re-enable them as they start passing.

See https://github.com/BurntSushi/toml-test for details

We are skipping all tests that `toml_edit` fails with the expectation
that we'll use the ignores as the task list for what is left towards
toml 1.0 and re-enable them as they start passing.

See https://github.com/BurntSushi/toml-test for details
@epage
Copy link
Member Author

epage commented Aug 17, 2021

I've have several branches that start to whittle down the list of ignores, starting with the easy ones to help bring me up to speed on the code base and combine (I'm more of a nom person).

I can add all of the commits to this PR, put up a PR with all of the commits after this, or put up a PR one at a time for each set of tests that starts passing. Let me know what you're preferred approach is.

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.

2 participants