FrontMatter: new subparser parser run from Markdown parser #3311
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
masatake
force-pushed
the
frontmatter
branch
3 times, most recently
from
86516fc to
fd0b229
Compare
Signed-off-by: Masatake YAMATO <[email protected]>
Signed-off-by: Masatake YAMATO <[email protected]>
masatake
force-pushed
the
frontmatter
branch
2 times, most recently
from
a113724 to
2cbb25f
Compare
Codecov Report
@@ Coverage Diff @@
## master #3311 +/- ##
==========================================
+ Coverage 85.31% 85.33% +0.02%
==========================================
Files 212 214 +2
Lines 49987 50086 +99
==========================================
+ Hits 42645 42740 +95
- Misses 7342 7346 +4
Continue to review full report at Codecov.
|
…tream By calling makePromise() with passing (0, 0, 0, 0) as arguments specifying the area, you can run a guest parser on the whole the area of the current input file. Internally, the main part reuses the current input stream for the guest parser. I found there is a case that it is impossible to reuse the current input stream in the guest parser; the current input stream is opened as as FILE based MIO and the guest parser needs a MEMORY based MIO. In this case, the main part should abort reusing and open a new MEMORY based MIO derived from the underlying FILE based MIO. However, reopening is not easy because the main part has no reliable way for calculating the area information for the MEMORY based MIO. The calculation is needed because the caller just passes (0, 0, 0, 0) as the area information. Till we can find a good way for calculating the area, what we can do is just printing warnings. Signed-off-by: Masatake YAMATO <[email protected]>
…exible Signed-off-by: Masatake YAMATO <[email protected]>
They were derrived from ansibleplaybook.c. Signed-off-by: Masatake YAMATO <[email protected]>
Signed-off-by: Masatake YAMATO <[email protected]>
In this version, just extracting "foo" in "title: foo" written in Yaml. JSON(;;;) and TOML(+++) are not supported yet. Close universal-ctags#3032. Signed-off-by: Masatake YAMATO <[email protected]>
|
How is this meant to be used? I tried several ways but the Are there currently efforts to extend parsing to full YAML? |
|
Could you show the input file? I also want to know the name of the file. |
|
Just a quick try with a file name ---
title: Some title
---
# Foo
This is a test.I am running on version 6.1.0. |
You may have to add |
|
Indeed, it works with |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In this version, just extracting "foo" in "title: foo" written
in Yaml. JSON(;;;) and TOML(+++) are not supported yet.
Tagging
a,b, andcintags: [ a b c ]is another TODO item.Much more work is needed in the Yaml parser.
Close #3032.