I've been investigating dotLog. I just wanted to let you know how much I like it. dotLog is minimal, that's nice; personally, I would keep it that way. Start a new project if you want more features. Here's what I've had time to suss so far...
constconcatS=add=(a,b)=>a+bdotLog.describe("function add",[{label:"add is a function",rule:(typeofadd==='function')},{label:"add takes two arguments",rule:(add.length===2)},{label:"add - Adds two numbers together; add(5, 4) returns 9",rule:(add(5,4)===9)},{label:"Add should return a value of type number, if passed two numbers",rule:(typeofadd(5,4)==='number')}])dotLog.describe("function concatS",[{label:"concatS is a function",rule:(typeofconcatS==='function')},{label:"concatS takes two arguments",rule:(concatS.length===2)},{label:"concats two strings together; concatS('Super', 'man') returns 'Superman'",rule:(concatS('Super','man')==='Superman')},{label:"concatS should return a value of type String if passed two strings",rule:(typeofconcatS('Super','man')==='string')}])
Keep up the good work Ady. I will be using dotLog.
:)
AND THERE IS MORE! How about dotLog described by dotLog
dotLog.describe("dotLog",[{label:"dotLog is an Object",rule:(typeofdotLog==='object')},{label:"dotLog has two properties",rule:(Object.keys(dotLog).length===2)},{label:"dotLog.describe is a function",rule:(typeofdotLog.describe==='function')},// {pending tests here to get it working in node.js console},// { and so on, and so on. I think you get the idea! }])
Of course, I'm just kidding. You really should'nt have something that is'nt tested, testing itself! But it was just a moment of madness.
You are so simply the best mate!!! And that’s very motivating that you could already find use for it.
You just became the official first adopter lol.
Thanks and let’s keep at it.
Cheers
Remember, take your time, don't rush it. Anything worth doing is worth doing well.
:-)
Catch you later.
PS.
Incidentally, when I first took a quick look at the dotLog code I did'nt have much time, but I noticed within the .describe method you were mapping over the testSet array and also that testSet contained objects with two properties label and rule; but still the "penny had not dropped" (ie. I had not got that aha moment). When I looked again at dotLog, some hours later, I then found your .png file(console-test-call.png) and instantly new what was going on.
Now, I'm just telling you this so that you know how important the example you provided in console-test-call.png was to understanding your code.
I think that, for me atleast, was something worth remembering.
Just thought I'd give you a heads up on a new log function I propose for dotLog. It basically addresses the issue of logging to nodejs. ie. after the environment that dotLog is running in has been detected, it selects the correct syntax for console.log in node or browser.
I've put it up on repl.it just for a quick preview.
Great I think we have similar ideas on that. I looked at a package called colors yesterday for the node side of things. The next step was to find a way to detect the environment and to do the appropriate output.
I’m glad you beat me to it 😀
Yes, I saw the colors package, but thought it might be a case of a "sledgehammer to crack a nut"; so decided not to. However, Ady, dotLog is your project and of course you should always have the final say since only you know which way you want to take it.
No no it's not mine it's open source lol :) The best approach should prevail. I like the simplicity of what you have put together. When I did my initial research colors was the first option that came up. The idea will be to have something as lean as possible.
Please feel free to suggest alternatives and may the one that makes most sense win. It will be of great benefit if you feel entirely enabled to make or suggest whatever you see fit. Cheers :)
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hey Ady,
I've been investigating dotLog. I just wanted to let you know how much I like it. dotLog is minimal, that's nice; personally, I would keep it that way. Start a new project if you want more features. Here's what I've had time to suss so far...
Keep up the good work Ady. I will be using dotLog.
:)
AND THERE IS MORE! How about dotLog described by dotLog
Of course, I'm just kidding. You really should'nt have something that is'nt tested, testing itself! But it was just a moment of madness.
All the best :-)
You are so simply the best mate!!! And that’s very motivating that you could already find use for it.
You just became the official first adopter lol.
Thanks and let’s keep at it.
Cheers
You keep at it mate!
Remember, take your time, don't rush it. Anything worth doing is worth doing well.
:-)
Catch you later.
PS.
Incidentally, when I first took a quick look at the dotLog code I did'nt have much time, but I noticed within the .describe method you were mapping over the testSet array and also that testSet contained objects with two properties label and rule; but still the "penny had not dropped" (ie. I had not got that aha moment). When I looked again at dotLog, some hours later, I then found your .png file(console-test-call.png) and instantly new what was going on.
Now, I'm just telling you this so that you know how important the example you provided in console-test-call.png was to understanding your code.
I think that, for me atleast, was something worth remembering.
Hey Ady,
Just thought I'd give you a heads up on a new log function I propose for dotLog. It basically addresses the issue of logging to nodejs. ie. after the environment that dotLog is running in has been detected, it selects the correct syntax for console.log in node or browser.
I've put it up on repl.it just for a quick preview.
repl.it/@johnboy5358/dotLog
cheers :-)
Great I think we have similar ideas on that. I looked at a package called colors yesterday for the node side of things. The next step was to find a way to detect the environment and to do the appropriate output.
I’m glad you beat me to it 😀
Yes, I saw the colors package, but thought it might be a case of a "sledgehammer to crack a nut"; so decided not to. However, Ady, dotLog is your project and of course you should always have the final say since only you know which way you want to take it.
:-)
No no it's not mine it's open source lol :) The best approach should prevail. I like the simplicity of what you have put together. When I did my initial research colors was the first option that came up. The idea will be to have something as lean as possible.
Please feel free to suggest alternatives and may the one that makes most sense win. It will be of great benefit if you feel entirely enabled to make or suggest whatever you see fit. Cheers :)