File Explorer app module: correct notification event argument names#18317
Closed
josephsl wants to merge 1 commit into
Closed
File Explorer app module: correct notification event argument names#18317josephsl wants to merge 1 commit into
josephsl wants to merge 1 commit into
Conversation
…nProcessing -> notificationProcessing (argumetn name/resolving TypeError)
5 tasks
Contributor
Author
|
Superseded by #18319, closing. |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Quick follow-up:
Link to issue number:
None
Summary of the issue:
File Explorer app module uses title case for notification event handler argument names.
Description of user facing changes:
None
Description of developer facing changes:
File Explorer's notification event argument names are corrected.
Description of development approach:
Argument name corrections:
Testing strategy:
Manual: make sure UIA notification events are raised without TypeError tracebacks.
Known issues with pull request:
None
Code Review Checklist:
@coderabbitai summary