[usability] quoteNone type in quote makes coding a pain

[gadicc]

As reported by @dtslvr in #416:

I have upgraded to [email protected] and have the following type error: Property 'currency' does not exist on type 'QuoteNone' for this snippet:

const quotes = await yahooFinance2.quote(['TSLA']);

for (const quote of quotes) {
  console.log('currency', quote.currency);
}

How can I deal with QuoteNone?

[gadicc]

As I stated there, in the meantime you workaround this like:

  if (quote.quoteType !== "NONE")
    console.log('currency', quote.currency);

but that's a pain and we can do better.

[gadicc]

🎉 This issue has been resolved in version 2.1.8 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀

[gadicc]

Big thanks to @dtslvr who noticed this so soon and reported straight away 🙌🎉

[dtslvr]

Big thanks to @dtslvr who noticed this so soon and reported straight away 🙌🎉

Thanks a lot for providing a solution that quick! 🤩

[gadicc]

Sure... the quoteNone thing was just in the last release so if when we unintentionally make the developer experience worse with a release we try fix it up as quick as we can :) So early reports like yours really help 🙏