Closed cshung closed 5 years ago
In this iteration, I fixed the obvious stuff. Now I know go use casing to determine exports. For non-export functions, it appears to me that the existing convention is to not comment them, so I simply deleted the comment.
Also tests are needed.
I will try to add one - so expect
a new iteration that comes with test, pun intended. :)
@skalle
Modified the ExpectTest
to do two expect
calls in a row to make sure we don't consume the whole buffer after the first expect
call.
@skalle
@skalle
Hey Andrew.
One last thing , could you add an Option to enable/disable this behaviour. Might be workflows out there relying on the current way it's done.
Hey. Sorry again for the slow replies.
Thx. a lot for fixing this, making go Expect better for everyone.
This is intended to fix issue #27