Skip to content
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

chore(analytics): enable linting on __tests__ #13430

Merged
merged 3 commits into from
May 29, 2024
Merged

Conversation

HuiSF
Copy link
Member

@HuiSF HuiSF commented May 24, 2024

Description of changes

See each commit message for details.

Issue #, if available

Description of how you validated changes

Checklist

  • PR description included
  • yarn test passes
  • Tests are changed or added
  • Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

@HuiSF HuiSF requested a review from a team as a code owner May 24, 2024 22:05
@HuiSF HuiSF force-pushed the hui/chore/analytics/lint-test branch from 9b0cd1e to caacf4e Compare May 24, 2024 22:11
@@ -46,7 +46,7 @@ describe('Analytics Personalize API: flushEvents', () => {
await new Promise(process.nextTick);
expect(mockResolveConfig).toHaveBeenCalledTimes(1);
expect(mockResolveCredentials).toHaveBeenCalledTimes(1);
const { trackingId, ...configWithoutTrackingId } = mockPersonalizeConfig;
const { trackingId: _, ...configWithoutTrackingId } = mockPersonalizeConfig;
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do we even need to keep trackingId if we are not using it?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This expression was for removing the trackingId property while creating a new copy from the mockPersonalizeConfig, I didn't want to refactor it completely from the original code.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

i think this might be missed artifact right? We should either check if trackingId's value or remove it , IMO. but non blocking so i will approve this PR :)

@HuiSF HuiSF force-pushed the hui/chore/analytics/lint-test branch from caacf4e to fea056c Compare May 29, 2024 16:24
@HuiSF HuiSF merged commit 7012646 into main May 29, 2024
30 checks passed
@HuiSF HuiSF deleted the hui/chore/analytics/lint-test branch May 29, 2024 16:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants