Skip to content

Switch Promise chaining to async-await syntax. #82

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

Merged
merged 5 commits into from
Oct 31, 2022
Merged

Switch Promise chaining to async-await syntax. #82

merged 5 commits into from
Oct 31, 2022

Conversation

lgarron
Copy link
Contributor

@lgarron lgarron commented Oct 28, 2022

This will make future PRs like #81 easier to author and review.

The functionality (and published build compat) should be exactly the same, so the existing tests should cover this change.

This will make future PRs like #81 easier to author and review.
@lgarron lgarron requested a review from a team as a code owner October 28, 2022 00:58
@primer-css
Copy link

👋 Hello and thanks for pinging us! This issue or PR has been added to our inbox and a Design Infrastructure first responder will review it soon.

  • 🎨 If this is a PR that includes a visual change, please make sure to add screenshots in the description or deploy this code to a lab machine with instructions for how to test.
  • If this is a PR that includes changes to an interaction, please include a video recording in the description.
  • ⚠️ If this is urgent, please visit us in #primer on Slack and tag the first responders listed in the channel topic.

@jonrohan jonrohan requested a review from keithamus October 28, 2022 01:39
Copy link
Contributor

@keithamus keithamus left a comment

Choose a reason for hiding this comment

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

LGTM

Co-authored-by: David Graham <david.malcom.graham@gmail.com>
@lgarron lgarron merged commit 46d0d7d into github:main Oct 31, 2022
@lgarron lgarron deleted the lgarron/async-await branch October 31, 2022 18:41
@lgarron
Copy link
Contributor Author

lgarron commented Nov 14, 2022

It seems this failed CI when merging. I'e been taking occasional pokes at it to figure out why, and it occurred to me today to try 7f8fbf0b — the previous merge. It also fails now.

https://github.com/github/include-fragment-element/actions/runs/3363846846/jobs/5577516226 failed with Chrome Headless 109.0.5394.0 while https://github.com/github/include-fragment-element/actions/runs/3114615886/jobs/5050656193 passed with Chrome Headless 108.0.5319.0, I wonder if that's it.

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