Fix priority type issue in extension registration #778
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Avoid a type issue (where string is expected to be an `int` but is instead a `string`) by providing the `priority` argument explicitly. By default, Codeception would append a `string` argument to the event registration that would be interpreted as the priority.
lucatume
force-pushed
the
v4-fix-event-subscription-type-issue
branch
from
ab5d662 to
4af892f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Avoid a type issue (where string is expected to be an
intbut isinstead a
string) by providing thepriorityargument explicitly.By default, Codeception would append a
stringargument to the eventregistration that would be interpreted as the priority.