Skip to content

Make parse_summary public? #265

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.

Sign up for GitHub

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

Jump to bottom
Closed
Rufflewind opened this issue May 5, 2017 · 2 comments
Closed

Make parse_summary public? #265

Rufflewind opened this issue May 5, 2017 · 2 comments
Labels
A-API Area: API M-Discussion Meta: Discussion S-On-hold Status: On hold

Comments

@Rufflewind
Copy link
Contributor

Could parse_summary() be made public? Currently in order to parse SUMMARY.md it’s necessary to run either init() or test(), which is undesirable due to their other side-effects.
@azerupi
Copy link
Contributor

azerupi commented May 5, 2017

I think it would be good to make it public too, however... It is in a terrible state right now so I am not sure how useful it would be.

@azerupi azerupi added A-API Area: API M-Discussion Meta: Discussion S-On-hold Status: On hold labels May 15, 2017
@Michael-F-Bryan Michael-F-Bryan mentioned this issue Jun 24, 2017
Closed
4 tasks
@Michael-F-Bryan
Copy link
Contributor

The summary parser was updated in #491, with the docs for the mdbook::book module being fleshed out in be4654c. The equivalent of parse_summary() will be available in the next release (either v0.0.29or0.1.0`) 🎉

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
A-API Area: API M-Discussion Meta: Discussion S-On-hold Status: On hold
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@Rufflewind @azerupi @Michael-F-Bryan