When writing specifications for work, many of them have the same patterns over and over again. When training people to write specifications for the first time, it can be helpful to provide templates that they can rely on so they do not make mistakes.
What it does
Dynamically template designs.
How I built it
I used full stack Clojure + Clojurescript.
Challenges I ran into
- I get tired sometimes.
- Clojurescript has tricky error sometimes and one must be careful not to explode everything
- I had to make a framework managing many text boxes because I didn't want to do too much string parsing, which meant that I had to remake several functions you take for granted in text editors.
Accomplishments that I'm proud of
Honestly, pride is a bit of a vice, so I'd rather not have too much of it.
What I learned
I got to play with clojurescript for the first time on a larger scale.
What's next for ShoutSpec
Better looking output files. I want the output to be a subset of markdown. At the momement there is only one type of point/label. It will be fairly trivial later to have different types of point, like:
- Immutable headings
- Name-value headings
- Code snippets. And because it's running on clojurescript I ought to be able to immediately evaluate these. :)
Another thing to do is create a way of importing templates externally.