It depends on the flow that you want in your code.
The benefit of async/await is not having to deal with callbacks and maintain what looks like a synchronous flow.
However, only using async/await has drawbacks, so that's where you might want to use
callbacks in .then() or .catch() to only handle some things like data transformation and error catching.
So you could handle your data with another .then(), and that's totally valid. Just depends on code style preference.
There are a couple of things that confuse me.
Second is that you're already dealing with callbacks. You've got callbacks when you pass data through a then and when you handle errors. So I don't quite see what you're avoiding by using this method.
That's why I am a bit confused as to what you're supposed to be improving on. Mind you, I'm not saying that you're not getting anything out of it. I'm saying that I don't see what you're getting out of it that wouldn't be improved by ditching async/await altogether.
Bonus track: A lot of people do say that async/await makes your asynchronous code look synchronous. I find it an odd statement, though, as promise syntax looks a lot more like these synchronous snippets of code:
const transformNumbers = array => array
const checkAdjacent = number => number
.some((x, i, a) => x == a[i - 1])
And more synchronous code would look like that if the TC39 guys finally implemented the pipeline operator.
What async/await does seem to do is to make asynchronous code look more imperative than promises. So maybe that's a thing you're getting by using your method?
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.