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 parse errors when single quotes are present in a table name #71

Merged
merged 1 commit into from
Feb 3, 2020

Conversation

sdispater
Copy link
Member

Fixes #70

@codecov-io
Copy link

codecov-io commented Feb 3, 2020

Codecov Report

Merging #71 into master will not change coverage.
The diff coverage is 100%.

Impacted file tree graph

@@           Coverage Diff           @@
##           master      #71   +/-   ##
=======================================
  Coverage   91.58%   91.58%           
=======================================
  Files          10       10           
  Lines        2164     2164           
=======================================
  Hits         1982     1982           
  Misses        182      182
Impacted Files Coverage Δ
tomlkit/parser.py 96.15% <100%> (ø) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update f90b668...b457973. Read the comment docs.

@sdispater sdispater merged commit de23e48 into master Feb 3, 2020
@sdispater sdispater deleted the issue-70-fix-for-string-delimiter-in-table-name branch February 3, 2020 22:07
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.

Apostrophe (single-quote) in key string causes problems
2 participants