Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. ItĀ collects links to all the places you might be looking at while hunting down a tough bug.
And, if youāre still stuck at the end, weāre happy to hop on a call to see how we can help out.
Adopt await/async/fetch?
See original GitHub issuerelated #19060
Howdy folks!
Hope all of your current projects are going well, Iāve seen some great work come up via my twitter feed.
After a little searching through previous issues, Iāve found a couple regarding async/await and have also spotted relevant sections within the code base however my searches have come up empty regarding the use of fetch. What is everyoneās thoughts on some movements towards async/await/fetch?
Currently the only thing within src that uses async/await is the loaders/ObjectLoader.js
Within examples thereās the LDrawLoader.js
ā¦but thatās about it.
Yes, yes, I can see the old functions have been wrapped in new Promiseās ā¦ but, oh I dunno, does that seem like only half the job done?
Issue Analytics
- State:
- Created 2 years ago
- Comments:8 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
Since we have already invested quite a lot of time this year in modernizing the code base, Iām hesitant in doing more in that regard in the next time. Especially if no concrete problem is solved with adapting new language features.
That would change how most of the examples are structured now though. Plus it adds complexity in order to achieve the same š¤·āāļø