MongoDB syntax

[airs0urce]

I applied changes as we discussed here: #2502

And also I have one question. I see with default theme tokens "builtin" and "string" have same color which visually looks like parsing has been broken:

In some themes "builtin" token has different color, not like "string" token, which looks good:

Question is - is there any recommendations by making "builtin" looks different from string with default theme?
Sure, I could create another theme and use it, but if the pull request will be approved, for people who decides to use this syntax it will be working bad by default like in the first screenshot.

[airs0urce]

Another way - I could name that token not "builtin", but something that has different color, but then meaning will be lost, which is bad too

[RunDevelopment]

You could use an alias. If you define class-name as an alias, the builtin classes will be highlighted in the same color as function in the default theme and the color in Tomorrow Night will remain the same.

[airs0urce]

@RunDevelopment
Thank you, I set "keyword" as alias:
alias: "keyword"

Didn't use "function" as generic JS function and mongodb function should be highlighted different.
Looks like everything is ready now.

[RunDevelopment]

Looks good @airs0urce!

A few minor nits and then we can merge this.

[airs0urce]

@RunDevelopment yes, agree about everything, will make the changes.
But not sure about "url" and "ip". The goal of adding them is to be able to easy catch those entities inside long string, for example I have logs written in MongoDB, I have long stack traces there and it will help to parse logs by eyes more quick:

If we highlight only full string containing URL or IP it will break the original idea of adding highlight because it's easy to catch URL or IP if it's fully inside string. So, if you think that false positives possible then I can just remove url and ip from the definition. Or I can change as you suggested, but right now not sure if it will be useful if it's done this way.

[RunDevelopment]

I have logs written in MongoDB, I have long stack traces there and it will help to parse logs by eyes more quick

If that was the explicit intention, then it's ok to keep it as is.

[airs0urce]

@RunDevelopment Yes, it was explicit. many developers use MongoDB for logging purpose, so it should help to parse strings by eyes.

[RunDevelopment]

Thank you for contributing @airs0urce!