Closed ryoppippi closed 5 days ago
Name | Link |
---|---|
Latest commit | 3d3284d9bcd808b536dfbb21a1f3e826b7068693 |
Latest deploy log | https://app.netlify.com/sites/melodious-froyo-4871f8/deploys/6672193abafeaf00080b9531 |
Deploy Preview | https://deploy-preview-510--melodious-froyo-4871f8.netlify.app |
Preview on mobile | Toggle QR Code...Use your smartphone camera to open QR code link. |
To edit notification comments on pull requests, go to your Netlify site configuration.
I don't know. I don't feel it's useful TBH. In many cases we want to have async
for functions just to make the return as promise, and making it easier for future await statement. This feels like could be a footgun to me that also a bit dangerous to change the runtime behavior. I don't think I will take this. Thanks.
https://typescript-eslint.io/rules/require-await
Description
Linked Issues
Additional context