-
-
Notifications
You must be signed in to change notification settings - Fork 97
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
test(runtime-vapor): api lifecycle hooks #215
Conversation
✅ Deploy Preview for vapor-repl ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for vapor-template-explorer ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Size ReportBundles
Usages
|
type DebuggerEvent, | ||
ITERATE_KEY, | ||
type InjectionKey, | ||
type Ref, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It gets sorted automatically by lint-staged.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I see that we are mixing the use of it()
and test()
function names, perhaps we can unify them into one? Other than that it looks good to me.
12fc70d
to
a265416
Compare
Indeed. I changed everything to "it"! |
resolve #164
relates: feat(runtime-core): implement debug hook #183
Regarding the lifecycle hook, I wrote tests based on the cases in packages/runtime-core/tests/apiLifecycle.spec.ts, but there seem to be some points where the behavior is incorrect.
I added FIXME to the test cases and created an issue on #216.