not valid stock symbol weird output

[jacksteussie]

Issue Label:

• [X] Bug
• [ ] New feature
• [ ] Enhancement
• [ ] New component

Description: I get the correct output when I do:

bash -x stocks nvda

But when I do just:

stocks nvda

I get the not a valid stock symbol error.

If its a bug make sure to include this section.

OS and OS version:

• [ ] Mac
• [ ] Linux 32 Bit
• [X] Linux 64 Bit
• [ ] Windows 32 Bit
• [ ] Windows 64 Bit

OS Version: Fedora 33

[navanchauhan]

This is because of changes made to the API service being used. It now requires an API key. The bash snippet will be needed to be updated to provide the API key.

https://github.com/alexanderepstein/Bash-Snippets/blob/97a1c0d6358264a50ca0c6e221b74ea1cb72b372/stocks/stocks#L86-L94

Output of bash -x stocks nvda

...
+ unset response
+ printStockInformation NVDA
++ httpGet https://financialmodelingprep.com/api/v3/company/profile/NVDA
++ case "$configuredClient" in
++ curl -A curl -s https://financialmodelingprep.com/api/v3/company/profile/NVDA
+ stockProfile='{"Error Message" : "Invalid API KEY. Please retry or visit our documentation to create one FREE https://financialmodelingprep.com/developer/docs"}'
++ httpGet https://financialmodelingprep.com/api/v3/stock/real-time-price/NVDA
++ case "$configuredClient" in
++ curl -A curl -s https://financialmodelingprep.com/api/v3/stock/real-time-price/NVDA
+ stockPrice='{"Error Message" : "Invalid API KEY. Please retry or visit our documentation to create one FREE https://financialmodelingprep.com/developer/docs"}'
+ export PYTHONIOENCODING=utf8
+ PYTHONIOENCODING=utf8
+ AccessJsonElement '{"Error Message" : "Invalid API KEY. Please retry or visit our documentation to create one FREE https://financialmodelingprep.com/developer/docs"}' profile companyName
+ echo 'NVDA: Not a valid stock symbol'
NVDA: Not a valid stock symbol
+ exit 1

As you can see the error message states the API key is invalid. You can either patch the snippet yourself and pass a free API key you can get from their website or you can wait until this issue is fixed ( but even then you will have to generate the API key yourself and put it in you ~/.bashrc, ~/.bash_profile or ~./zshrc as the API key cannot be provided with the bash-snippets code.

[alexanderepstein]

Hmm so if they now require an api key it means I should try to find another service that does it for free, my goal with bash-snippets is to prevent any need for setup and api keys are usually something I try to work around. If anyone would like to take up replacing the current stocks api with a different one that didn't use an API key I would most likely merge the changes.