Previously, we were using the `color` property to determine the color of the border around `<dialog
/>` elements. The issue with this is that it requires the text color to match the border color. I've
fixed this by moving the border color declarations into the `box-shadow` property.
We no longer need to build the entire framework to lint it, so I've removed the build step from the
pre-commit hook and replaced it with just stylelint.
The dialog styles added by @sophi-est weren't being loaded into the compiled stylesheet. I've added
them to the elements index file and moved the rounded corners styles into and `.is-rounded` modifier
class.
I did a dumb. I changed the name of he script that updates the package headers before a release, but
I didn't tell `semantic-release-exec` that I'd changed it. 😬
I've add a script to handle automatically updating bot the CSS and SCSS headers with the relevant
information before publishing. This update is handled as part of `semantic-release`'s preparation
step.
I've moved the SCSS functions file into the `scripts` directory where I think it makes a bit more
sense. I've also abstracted most of the functionality from it so I can also use it in
`semantic-release`'s preparation step.
The `version` field in the `package.json` file doesn't serve any real purpose for us since
`semantic-release will handle adding and updating it automatically.
Hehehehe, this is really cool. I've removed the hardcoded version number from `nes.scss` and
replaced it with a custom function. This function does all sorts of cool stuff.
1. **Injects the framework version from `package.json`
This prevents us from having to inject the version number manually.
2. **Adds build info…**
The branch that the CSS was built from, when it was built, what version of Node was used… All of the useful information that we could possibly provide. If it’s built on CircleCI, it even includes the build number.
3. **…but not too much build info**
If the build is running against the `master` branch, we only inject the framework version. No need to bloat production builds with all the other junk. 😁
