* Unfortunately @joshbruce lost some credibility by a post edit with an edit misusing the OpenUserJS brand so respectfully removing listing.
NOTE:
* This is probably why no-one else has done this
Ref:
* #1233
with
> LGTM!
... apparently it wasn't and shouldn't have been merged without all parties consent.
* This is the nomenclature and the compromise that can remove the `@` symbol by linking... similar to mentioning GH teams
* Using relative URLS unless you plan on putting this on a custom domain
* Since no-one elses `@`nick mention is hyperlinked not doing mine for symmetry
* Not everyones project is hosted on GH btw... so `Project` is neutral... typically we use the word `Development`
* No badge column now so remove linkage reference
* Not everyone's project name matches their DN so that's why I put the `@` symbol in for the Organization *(username on GH)*
* Usually this is set to these values but I turned it off for this PR in case it blew up GH md. Had this happen once on another project. So crosses-fingers and things
Ref:
* 92f0ae232f/.editorconfig
Technically this makes me a Contributor according to GH ;) LOL j/k I do what I can when I can. :)
<!--
If release PR, add ?template=release.md to the PR url to use the release PR template.
If badging PR, add ?template=badges.md to the PR url to use the badges PR template.
Otherwise, you are stating this PR fixes an issue that has been submitted; or,
describes the issue or proposal under consideration and contains the project-related code to implement.
-->
**Marked version:**
0.3.19
<!-- The NPM version or commit hash having the issue -->
**Markdown flavor:** Markdown.pl|CommonMark|GitHub Flavored Markdown|n/a
GitHub Flavored Markdown *(Perhaps CommonMark down the line)*
## Description
- Fixes the request at https://github.com/markedjs/marked/issues/1232#issuecomment-382747699 <!-- (if fixing a known issue; otherwise, describe issue using the following format) -->
<!--
If no issue exists that you're aware of. The maintainers should be able to figure out if it's a duplicate.
-->
## Expectation
<!--
Describe the output you are expecting from marked
-->
GitHub Flavoured Markdown of course.
## Result
<!--
Describe the output you received from marked
-->
Continued, awesome, markdown for > ~9437 users ... denoted.
## What was attempted
<!--
Describe what code combination got you there
-->
A subtle, indirect, request for Usership addition in a comment. :) Hopefully I got the badge of honour correct.
## Contributor
- [ ] Test(s) exist to ensure functionality and minimize regression (if no tests added, list tests covering this PR); or,
- [ ] no tests required for this PR.
- [ ] If submitting new feature, it has been documented in the appropriate places.
## Committer
In most cases, this should be a different person than the contributor.
- [ ] Draft GitHub release notes have been updated.
- [ ] CI is green (no forced merge required).
- [ ] Merge PR
* Rename undefined variable.
* Delete unneeded quotes.
* Fix alignment in the actual output from the code example
and make it more close to the "Output:" example
(otherwise, the indentation of the "<h1>" line will be out of order).
