-
Notifications
You must be signed in to change notification settings - Fork 82
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
remove "debug" property #477
Comments
@G-Rath @oscard0m @wolfy1339 I'd like to remove the Any other breaking changes we should address as part of v9? |
Possibly not related, but I think we should split up |
That doesn't sound like a breaking change? |
we could adjust the I'm not fussed on how far we actually take this at runtime, since I think it'll be overkill to verify the returned object is most definitely the event by way of checking for every required property + types + etc but we could do a basic That's if we want to do anything at all at runtime - I'm happy if we just want to say "your transformation should return an extension of the original event object - our types assume you do but we don't actually enforce this at runtime" (which is what we're currently doing) |
I agree, I wouldn't do any checks at runtime, just document that it should, and implement the types accordingly. Similarly, we don't implement any client-side validation for all the REST API endpoint methods any more, we just provide the correct types. It has worked out great |
🎉 This issue has been resolved in version 9.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
We introduced a
log
option as a replacement for thedebug
module in #457. As part of the next breaking release, we shoudl remove thedebug
module altogether.The text was updated successfully, but these errors were encountered: