-
Notifications
You must be signed in to change notification settings - Fork 19
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
Accessing promise index instead of index' result #67
Comments
Hey guys, any chance to see this fix reviewed (and merged 😁) ? Thanks for your feedback 🙏 ! |
Thanks @abudaan 🙏 . I didn't update the version number but I wrote the CHANGELOG with the Unreleased tag. Didn't know if I had to bump the version number manually. |
Oupsy, I just saw that I think that I didn't update the right CHANGELOG oO. Do I have to make a new PR to fix this ? |
No problem :) Thanks for your fix! |
@abudaan , I think that the npm update for the GCS adapter is missing, it's still |
Hi @abudaan, me again 😅 , sorry to bother you (again) but I think something went wrong with the build. I saw you tagged 1.0.8 but the output code does not include the patch. I git cloned your last commit, run Not sure of what's going on here 🤔 |
Summary:
There is a priority problem between the promise/await and array access. Fix this by prioritizing the promise result over then array access. It was causing the following error :
The code to reproduce
Tested on:
Node 20.12.2
NPM 10.5.0
Fix proposal
See #66
The text was updated successfully, but these errors were encountered: