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

fix: @typescript-eslint/no-floating-promises #11665

Merged
merged 43 commits into from
Jan 6, 2023

Conversation

sdstolworthy
Copy link
Contributor

Description of changes

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)
  • New AWS SDK calls or CloudFormation actions have been added to relevant test and service IAM policies
  • Pull request labels are added

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

@sdstolworthy sdstolworthy requested a review from a team as a code owner December 27, 2022 17:44
sobolk
sobolk previously approved these changes Dec 27, 2022
@sobolk
Copy link
Member

sobolk commented Dec 27, 2022

please run e2e.

@codecov-commenter
Copy link

codecov-commenter commented Dec 27, 2022

Codecov Report

Merging #11665 (730a909) into dev (2294cf8) will decrease coverage by 0.01%.
The diff coverage is 50.73%.

@@            Coverage Diff             @@
##              dev   #11665      +/-   ##
==========================================
- Coverage   50.22%   50.21%   -0.02%     
==========================================
  Files         705      705              
  Lines       34072    34083      +11     
  Branches     6993     7001       +8     
==========================================
+ Hits        17114    17116       +2     
- Misses      15478    15486       +8     
- Partials     1480     1481       +1     
Impacted Files Coverage Δ
...vider-utils/awscloudformation/utils/zipResource.ts 15.78% <0.00%> (ø)
...s/amplify-category-geo/src/commands/geo/console.ts 53.84% <0.00%> (ø)
...-category-storage/src/commands/storage/override.ts 71.42% <0.00%> (ø)
...ation/service-walkthroughs/dynamoDB-input-state.ts 7.35% <0.00%> (ø)
packages/amplify-category-xr/commands/xr/add.js 50.00% <0.00%> (ø)
packages/amplify-category-xr/commands/xr/remove.js 50.00% <0.00%> (ø)
packages/amplify-category-xr/commands/xr/update.js 50.00% <0.00%> (ø)
...amplify-cli-core/src/feature-flags/featureFlags.ts 81.55% <0.00%> (ø)
...c/extensions/amplify-helpers/auth-notifications.ts 45.05% <0.00%> (ø)
...extensions/amplify-helpers/resource-status-view.ts 65.00% <0.00%> (ø)
... and 39 more

📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more

@evcodes evcodes self-requested a review December 28, 2022 21:37
Comment on lines +273 to +280
do {
const { value, done: doneResult } = await asyncIterator.next();
done = doneResult;
if (done) {
break;
}
this.sendMessage(connectionContext, id, MESSAGE_TYPES.GQL_DATA, value);
}
} while (!done);
Copy link
Contributor

Choose a reason for hiding this comment

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

I don't know if we should use a do-while loop pattern in this case. The previous way seems cleaner and there's not many other do-while loops in our codebase

import {
addMapResource, addMapResourceHeadless, removeMapResource, updateMapResource, updateMapResourceHeadless,
} from './map';
import { addMapResource, addMapResourceHeadless, removeMapResource, updateMapResource, updateMapResourceHeadless } from './map';
Copy link
Contributor

Choose a reason for hiding this comment

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

how come the imports in this file aren't separated by new lines?

invokeAnalyticsAPIGetResources,
invokeAnalyticsPush,
} from './plugin-client-api-analytics';
import { invokeAnalyticsAPICreateResource, invokeAnalyticsAPIGetResources, invokeAnalyticsPush } from './plugin-client-api-analytics';
Copy link
Contributor

Choose a reason for hiding this comment

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

same question here

stack: deepestException.stack ?? 'undefined error stack',
})),
() =>
executeHooks(
Copy link
Contributor

@evcodes evcodes Dec 29, 2022

Choose a reason for hiding this comment

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

I think this should be async/awaited?

Comment on lines +436 to +438
resources.concat(resourcesToBeDeleted).filter((r: { service: string }) => r.service === AmplifySupportedService.LAMBDA_LAYER).length >
0
) {
Copy link
Contributor

Choose a reason for hiding this comment

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

This formatting is a bit weird

Copy link
Contributor

@evcodes evcodes left a comment

Choose a reason for hiding this comment

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

a few nits, none of which are blocking the PR

@sdstolworthy sdstolworthy merged commit 6c64717 into aws-amplify:dev Jan 6, 2023
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.

None yet

5 participants