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
(chore) add name
attribute to all language grammars
#2407
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Also please remove the extra changelog file you seemed to add.
src/languages/c-like.js
Outdated
@@ -197,6 +197,7 @@ export default function(hljs) { | |||
}; | |||
|
|||
return { | |||
name: 'C-like', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is just a foundation. No name needed.
src/languages/apache.js
Outdated
@@ -19,7 +19,8 @@ export default function(hljs) { | |||
begin: ":\\d{1,5}" | |||
}; | |||
return { | |||
aliases: ['apacheconf'], | |||
name: 'Apache', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please add “config” to match the title.
src/languages/julia.js
Outdated
@@ -86,6 +86,7 @@ export default function(hljs) { | |||
|
|||
// placeholder for recursive self-reference | |||
var DEFAULT = { | |||
name: 'Julia', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs to go in the return block not default.
Very nice work. Thanks for the contribution. |
You really should rebase this on master though. I meant I can work with this, but for future contributions the PR will be MUCH nicer and easier to review if you're starting from a clean master. |
name
Attribute(s)name
attribute to all language grammars
b6b85af
to
3c8f550
Compare
Done? Huh? Where am I now? |
My first intention was that I wanted to merge this commit onto your branch in Wow, this project is so crowded. I feel lost sometimes. |
lang_has_name is in master now and this commit chain is just crazy. You should hard reset your own master to upstream master and then cherry-pick your 2 commits back on top. (that's easiest if you don't know how to do the rebase) |
Sorry Git and Github can be a real pain if you aren't familiar with them. Have you been merging upstream master into your master (while also committing to your master)? That is bad mojo and will cause you all sorts of problems. This might be of interest: https://thoughtbot.com/blog/git-interactive-rebase-squash-amend-rewriting-history |
Have been using it for my personal project but never used it to collaborate with others.
That was from my previous pull request. I didn’t delete that repository after my pull has been merged and just continue creating a branch named The commit log data in my |
Yeah that's how you get everything messed up. Because the final merge of anything often isn't the same as what's in a PR... so now your history has diverged from upstream master and you start seeing everything twice... to avoid that your master should always be pinned to upstream master. You can fix it by a hard reset: # make sure upstream is a remote
git remote add upstream git@github.com:highlightjs/highlight.js.git
# checkout your master branch
git checkout master
# force reset your master to point to the SAME exact commit as upstream/master
git reset --hard upstream/master That's just to "fix" master... you should always do your work in branches and NEVER commit to master (when contributing to projects). If you keep your master clean then all you have to do is switch to it periodically and merge upstream:
Once you have your master sane again you can switch to your branch, hard-reset IT to master also and then |
If that's' too much let me know and I can probably finish this up myself. |
3c8f550
to
9822095
Compare
Doh, sorry for that |
Closes #2394
Related: #2400