-
-
Notifications
You must be signed in to change notification settings - Fork 22
[ReleaseBranch] Substitute v2-beta: Rework substitution logic #139
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
This includes SubstituteBase, SubstituteException, Arguments, Utilities
* move existing tests to regression folder * add RecordedArguments spec * create Utilities spec
* improve proxy creation function * use node contexts to simplify node logic * implement custom records set RecordsSet implements the higher order filter and map methods which get applied when retrieving the iterator. This increases performance as it doesn't create arrays on each .map or .filter -> the iterator yields only the end values with one iteration
resolves #46 * implement clearSubstitute * add clearSubstitute spec
Awesome work so far. Looking forward to it being ready for review! |
Thanks 😄 |
I see no issues with that, but then I think this project should also have its own CI pipeline. Because right now, it's hard to do, because everything is published using https://github.com/ffMathy/FluffySpoon.Publishers. |
That's what I wanted to suggest, it would great to have the release system in a Github Action. |
Indeed! Feel free to make an |
In the long run though, |
Sure, that sounds like a good idea 👍
We need a NPM api key, don't we? |
I already have a key 😊 if you can make it work with placeholder values for the key, I'll insert the real one as a GitHub secret 😊🙏 |
I just merged a publish github action, which publishes both to npm and github. |
The npm token name for the secrets is |
I tried committing something to retry now. Hopefully it works. @notanengineercom not sure what happened, but somehow your message got lost in translation. I'll try to follow up on it soon, so we can get this beautiful work out. As for coding styles though, I think you should re-add the semicolons, but we can do that later too. |
This branch is the base of v2 (feature branch).
It contains the base of the new structure.
All existing features are supported, with a few changes.
💥 Breaking Changes
👀
FluffySpoon.JavaScript.Testing.Faking/spec/regression/resolves.spec.ts
Lines 25 to 33 in 6893b7d
✨ New Features
👀
🎨 Improvements
👀