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

Update docs #1081

Merged
merged 45 commits into from
Feb 27, 2018
Merged

Update docs #1081

merged 45 commits into from
Feb 27, 2018

Conversation

joshbruce
Copy link
Member

@joshbruce joshbruce commented Feb 25, 2018

Description

This PR helps break up the README into more consumable chunks.

Submitter

  • Test(s) exist to ensure functionality works (if no new tests added, list which tests cover this functionality); or,
  • no tests required for this PR.

Reviewer

  • Draft GitHub release notes have been updated.
  • case_insensitive_refs is only failing test (remove once CI is in place and all tests pass).
  • All lint checks pass (remove once CI is in place).
  • Merge PR

@joshbruce joshbruce self-assigned this Feb 25, 2018
@Feder1co5oave
Copy link
Contributor

Josh, this is the third PR you've opened concerning updates to the README. Can you slow down a bit? I cannot follow you around in all these new issues.

Remember if you change your mind on some commits you make in the PR branch you can always rewrite them by git reset or git rebase and then git push --force, and the commits will be re-written. This is generally NOT safe to do on a shared public branch because it can "break" the branching history on the collaborators' local copies, but since this is a WIP and you're the only one pushing, it can be considered safe to do, before merging.

@joshbruce
Copy link
Member Author

That's fair. Not sure the other specific PRs you're referring to - I only have two opened at the moment: #1076 (0.3.17 release updating PR templates) and this one.

I believe the others might have been merged or closed...I did run into an issue where GitHub was listing my PRs as being from an "unknown repository," which I've never seen before now; therefore, some of the closings were due to that. Don't think I'll be opening any more new things for a bit. :)

Definitely understand the feeling though - this is what it felt like when @chjj and I were doing the organization thing - things were done before I could hit reply. ;)

@@ -0,0 +1,136 @@
## Extending Marked
Copy link
Member Author

Choose a reason for hiding this comment

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

@Feder1co5oave, @UziTech, and @styfle: Could use some help on the content here, I think. Purpose is to document and demonstrate overriding/extending the renderer, lexer, and parser...seems we are light on documentation there.

<li><a href="#parser">The parser</a></li>
</ul>

<h2 id="rederer">The renderer</h2>
Copy link
Member Author

Choose a reason for hiding this comment

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

The renderer...

Copy link
Member

Choose a reason for hiding this comment

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

Why are you using HTML here? Instead of <h2> you can use ## Renderer

Copy link
Member Author

Choose a reason for hiding this comment

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

Fair question. For the id attribute. Is there another way to get inline anchors to work properly using GitHub Markdown??

Copy link
Member Author

Choose a reason for hiding this comment

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

Consolidating comments from #1061: I've always run into issues there [GitHub automatically generating IDs]; so, normally end up doing it by hand. Also, could make it more difficult to use in a non-GFM setting; at least here we know the TOC will always work[...like pulling in the Markdown file into a separate context outside of the GFM markdown rendering.]

Copy link
Member

Choose a reason for hiding this comment

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

I typically let github generate it like so: https://github.com/styfle/copee#demo
But a TOC is a good point, you don't want to accidentally break it if you change the heading later.

- image(*string* href, *string* title, *string* text)
- text(*string* text)

<h2 id="lexer">The lexer</h2>
Copy link
Member Author

Choose a reason for hiding this comment

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

The lexer...

The lexer is...


<h2 id="parser">The parser</h2>
Copy link
Member Author

Choose a reason for hiding this comment

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

The parser...


The parser is...

***
Copy link
Member Author

@joshbruce joshbruce Feb 25, 2018

Choose a reason for hiding this comment

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

The current documentation for the lexer and parser

@joshbruce joshbruce changed the base branch from update-readme to master February 25, 2018 22:46
@joshbruce
Copy link
Member Author

joshbruce commented Feb 25, 2018

  1. Extensibility could use some more detail; doesn't necessarily need to be in this PR.
  2. Think this should be merged before Release 0.3.17 (template updates) - ?? #1076 to test the process on being able to update the release PR as long as the publish has not been run.
  3. This should give us a much tighter README (presence on NPM) and the foundation for a possible GitHub Pages site down the road (thanks for the recommendation and good looking out @styfle).

Josh Bruce added 4 commits February 25, 2018 21:56
JS seems off for USAGE_ADVANCED asyn highlighting
@joshbruce joshbruce added the RR - refactor & re-engineer Results in an improvement to developers using Marked, or end-users, or both. label Feb 26, 2018
This was referenced Feb 27, 2018
AUTHORS.md Outdated
- Tony Brix @UziTech
- Federico Soave @Feder1co5oave
- Tony Brix @UziTech - really good at the test harness and environment setup
- Federico Soave @Feder1co5oave - really good at the regex things
- Steven @styfle
Copy link
Member

Choose a reason for hiding this comment

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

Steven @styfle - good for nothing

😜

Copy link
Member Author

Choose a reason for hiding this comment

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

I honestly thought about putting: Good for lying in the weeds and randomly showing with a nugget of excess truth on operations before disappearing again. 😝

@joshbruce joshbruce merged commit 953002c into markedjs:master Feb 27, 2018
zhenalexfan pushed a commit to zhenalexfan/MarkdownHan that referenced this pull request Nov 8, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
RR - refactor & re-engineer Results in an improvement to developers using Marked, or end-users, or both.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants