INTL-231: Try checking for ignore lines within components

[alanknight-wk]

Motivation

Ignore comments of the form

(mui.MenuItem()
                ..component = Dom.div.elementType
                // ignore_statement: intl_message_migration
               ..value = 'audit-info'

don't work because we start looking for the ignore comment ahead of the full expression. Try looking for them ahead of the line as well. We don't want it to trigger on other lines in the sequence of calls, e.g.

(mui.MenuItem()
                ..component = Dom.div.elementType
                // ignore_statement: intl_message_migration
               ..value = 'audit-info'
               ..title = 'some translateable string'

so only look a depth of one token back. That probably won't catch every condition, but it's better than nothing and shouldn't have too many bad cases if it only looks back one.

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

• Tests were updated and provide good coverage of the changeset and other affected code
• Manual testing was performed if needed
  • Steps from PR author:
  • Anything falling under manual testing criteria outlined in CONTRIBUTING.md

Merge Checklist

While we perform many automated checks before auto-merging, some manual checks are needed:

• A Frontend Frameworks Design member has reviewed these changes
• There are no unaddressed comments - this check can be automated if reviewers use the "Request Changes" feature
• For release PRs - Version metadata in Rosie comment is correct

[aviary-wf]

Security Insights

No security relevant content was detected by automated scans.

Action Items

• Review PR for security impact; comment "security review required" if needed or unsure
• Verify aviary.yaml coverage of security relevant code

---

Questions or Comments? Reach out on Slack: #support-infosec.

[alanknight-wk]

Tried this on audit, it seemed to fix the issues.

[robbecker-wf]

QA+1 CI passes and testing manually shows that it works when adding the comment on the line before a string in the middle of a react component.

[robbecker-wf]

@Workiva/release-management-p

[rmconsole-wf]

+1 from RM