This is bug in current swift versions as compiler is not able to recognize the global actor context for a defer block, the discussion for this is going on swift forum and a PR with fix also available that should resolve this issue in future swift versions. For now, explicitly global actor context need to … Read more
async/await and promises are closely related. async functions return promises, and await is syntactic sugar for waiting for a promise to be resolved. The only drawback from having a mix of promises and async functions might be readability and maintainability of the code, but you can certainly use the return value of async functions as … Read more
Well, walking through the reasons in the “avoid async void” article: Async void methods have different error-handling semantics. Exceptions escaping from PrimeCustomTask will be very awkward to handle. Async void methods have different composing semantics. This is an argument centered around code maintainability and reuse. Essentially, the logic in PrimeCustomTask is there and that’s it … Read more
Since the main scope is not async, you will need to do an async anonymous function that calls your function and itself : (async function() { await yourFunction(); })(); Or resolve the promise : yourFunction().then(result => { // … }).catch(error => { // if you have an error })
You can call an async function from your EventListener. The first problem I see is that you are invoking the callback function right away in the second argument of window.addEventListener by including it as loadEdit() instead of loadEdit or () => loadEdit(). You have to give it a function as second argument, right now you … Read more
5 months later I’m coming back to answer my question (I’ve learned a lot since posting this question lol)…. First of all, since it is 5 months later I want to underscore that it is better to use the userEvent library instead of fireEvent if possible. I also would be remiss to not call out … Read more
After playing with the code I was able to figure it out. Here is the solution. public async Task DeleteSchoolTask(int schoolNumber, int taskDetailId) { var result = await GetTaskTypeAndId(taskDetailId); int taskId = result.Item1; string taskType = result.Item2; // step 1: delete attachment physically from server var fileService = new FileService(Logger, CurrentUser); var relativeFilePath = $”{schoolNumber}\\{Consts.RM_SCHOOL}\\{taskDetailId}”; … Read more
The struct approach wouldn’t work. If you want to asynchronously return an IAsyncEnumerator<T> value, you could use Task<IAsyncEnumerator<T>> with return Bar();. However, that would be unusual. It would be much more natural to create a new IAsyncEnumerator<T> that incorporates await SomeAsyncMethod() at the beginning of the asynchronous enumerable. To do this, you should use await … Read more
To answer your questions more directly: ConfigureAwait(true): Runs the rest of the code on the same thread the code before the await was run on. Not necessarily the same thread, but the same synchronization context. The synchronization context can decide how to run the code. In a UI application, it will be the same thread. … Read more
The return value will always be a promise. If you don’t explicitly return a promise, the value you return will automatically be wrapped in a promise. async function increment(num) { return num + 1; } // Even though you returned a number, the value is // automatically wrapped in a promise, so we call // … Read more