-
Notifications
You must be signed in to change notification settings - Fork 7
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
FED-1979 Add suggestor to replace null argument in dom callback #272
FED-1979 Add suggestor to replace null argument in dom callback #272
Conversation
Security InsightsNo security relevant content was detected by automated scans. Action Items
Questions or Comments? Reach out on Slack: #support-infosec. |
53c4386
to
e20ab23
Compare
e20ab23
to
dfced0c
Compare
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.
+10,
Excluded React DOM event callback props aren't used in the Workiva ecosystem in test files and non-test files:
sourcegraph
sourcegraph
Great test coverage!
bin/dom_callback_null_args.dart
Outdated
// See the License for the specific language governing permissions and | ||
// limitations under the License. | ||
|
||
export 'package:over_react_codemod/src/executables/dom_callback_null_args.dart'; |
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 haven't reviewed this PR, but I have the same question on all these - do we want to have just one null_safety_prep
that all these codemods can go into instead of adding a bunch of separate codemods?
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.
@sydneyjodon-wk I was wondering about that actually - I think thats a good idea...
Should I remove the individual bin/
executables here and in #273? Or can we add an aggregated executable in a follow-up PR without modifying these?
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.
Is there a reason we would need separate executables along with the aggregated one?
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.
Not necessarily - was just thinking we could create the aggregate executable in a single pr rather than having to push changes to two existing PRs
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.
oh yeah that works! I think we should remove the individual executables from both PRs though if we don't think they're needed if that's what you were asking!
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.
@sydneyjodon-wk done (in both PRs)
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.
+10, reup - just removed standalone executable
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.
This looks great, just had the same comments as the other one!
|
||
@override | ||
Future<void> generatePatches() async { | ||
_result = await context.getResolvedUnit(); |
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.
Wondering if this one doesn't need to be resolved either?
_result!.unit.accept(this); | ||
} | ||
|
||
static const callbackToSyntheticEventTypeMap = { |
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.
Are the values in this map just for testing purposes? I only see the keys being used in this file?
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 think this file can be removed too in favor of adding this to the null_safety_prep codemod
we will be moving this into an aggregate executable in a separate PR
5f8d940
to
04c3741
Compare
@sydneyjodon-wk I've made the necessary updates to get this running as part of the larger |
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.
+10 tested on web_skin_dart and Anna tested on w_comments as well! 🎉
@Workiva/release-management-p
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.
+1 from RM
Motivation
Changes
Release Notes
Review
See CONTRIBUTING.md for more details on review types (+1 / QA +1 / +10) and code review process.
Please review:
QA Checklist
null
literal as an argument, now have the correct empty synthetic event being passed instead.Merge Checklist
While we perform many automated checks before auto-merging, some manual checks are needed: