You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I put the details of the issue into this Clojure google group post. But the main issue is the case where my documentation inside of a _against-background_ block, is being ignored. I looked for lein-midje-doc examples that demonstrate this. But, say purnam or clortex, aren't using against-background blocks, that I can see. Is this expected behaviour, or a bug?
The text was updated successfully, but these errors were encountered:
twashing
changed the title
Arch documentation is failing inside of against-background macro
Arch Documentation Failing inside "against-background" block
Aug 18, 2014
Thanks for pointing this out. I'm aware of this fact but I'm not sure if I have time to implement the feature.
The point of midje doc is to allow writing of testable documentation, not to turn your midje tests into readable docs. As such, I decided to not implement every feature of midje but instead to just concentrate on the most basic.
There should always be a way to write it without against-background. I'm not a big fan if the macro as I find it sometimes breaks but that's another story altogether.
I put the details of the issue into this Clojure google group post. But the main issue is the case where my documentation inside of a against-background block, is being ignored. I looked for lein-midje-doc examples that demonstrate this. But, say purnam or clortex, aren't using against-background blocks, that I can see. Is this expected behaviour, or a bug?
—
Reply to this email directly or view it on GitHub.
I put the details of the issue into this Clojure google group post. But the main issue is the case where my documentation inside of a _against-background_ block, is being ignored. I looked for lein-midje-doc examples that demonstrate this. But, say purnam or clortex, aren't using against-background blocks, that I can see. Is this expected behaviour, or a bug?
The text was updated successfully, but these errors were encountered: