-
Notifications
You must be signed in to change notification settings - Fork 7
Should meeshkan record have --specs-dir and --mode options? #123
Comments
If you provide a mode it will create both logs and specs. So you can avoid running |
@aby2s Thanks! |
Bringing this issue back to LIFE and changing the heading because I think it's a discussion worth having. I'd vote to remove any Curious to hear others thoughts on this, particularly @aby2s because I know you implemented it in the first place. Also tagging @ksaaskil and @mikesol for more voices! 📣 |
I don't really like running cli commands though (or because) I work on Ubuntu. And if I were a user (and I could be), an unnecessary additional step would disappoint me a lot. |
Fair point considering you might be our current power user @aby2s 😆 Also @fornwall and I spoke with @mikesol this morning about what the "selling point" of Meeshkan is. It seems like we want to focus on the mocking aspect, with recording and building being supplements. In that case, being able to skip steps could make sense - plus then we could add (smarter) logging to track how people are building their specs/whether the calls they are making are adding anything new to the schema (or not). Considering all of the above, I'd maybe propose keeping it - but not focusing on it in the documentation yet. If we really lean into the mocking aspect, then we'll have to restructure the docs anyway - so then that would be a good opportunity to figure out how we want to introduce it. |
I can see how it's easier for users if they can avoid running the separate build step, with record taking care of schema building. For me, it just feels a bit awkward to write something like |
The text was updated successfully, but these errors were encountered: