var seasonEndDateSalmon = "10";
var seasonStartDateTrout = "03";
var seasonEndDateTrout = "10";
//Set year radio labels
var currentYear = new Date();
document.getElementById("currentYear").innerHTML = currentYear.getFullYear();
var nextYear = new Date();
document.getElementById("nextYear").innerHTML = nextYear.getFullYear() + 1;
Is what I have so far. Not much I know, getting brain block
'2017-03-28T21:47:53.832Z'
, then .832
is micro seconds? To my mistake I thought, that it is somehow connected to Z
. But as I understand now, that Z
in the end means, that time is in UTC and shift coresponding to specific timezone can be added.
I'm investigating how the code around matchers work and I would like to be able to throw debuggers in to step through it. Could anyone share their development environment setup?
My setup right now consists of a react app (using create-react-app) that includes the package. I used npm link
to point to the package on my local machine which appears to work when I open up node modules. However, my code changes do not appear - I suspect it is because it's referencing the minified version.
The docs state that grunt release
will build the minified version of the package. However, it also requires the tests to pass before it will run.