-
Notifications
You must be signed in to change notification settings - Fork 5
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
Introduce info string commands #56
Conversation
Nice work! Have seen briefly, but will look more tomorrow. |
30f5542
to
9507e19
Compare
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.
Very complex. (for a beginner of javascript)
But surprisingly working well. 👍
lib/config.js
Outdated
if (infoString === infoStringBefore) { | ||
const spacePosition = infoString.indexOf(" ") | ||
if (spacePosition !== -1) { | ||
const unkown = infoString.substr(0, spacePosition) |
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.
typo of unkown
.
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.
console.warn
's string too.
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.
@benevbright Thanks! I fixed it.
This prepares an API to create #19, #18, and #32. All those features will have very complex regular expressions and escaping. Therefore an API preparing those regular expressions and testing them centrally makes sense.
Every command in info strings consists out of:
+
=
(optional)regexp
,string
,number
,boolean
, ornull
; optional)Examples: See #19, #18, and #32