-
Notifications
You must be signed in to change notification settings - Fork 1
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
[BUG]: Clarify the provider
object name
#8
Comments
provider
object name
I changed the i.e nasdaq_provider = Provider() You should think about clarifying that you don't need to change the provider object and it can just be:
|
Hi, Thanks for raising this. I'd suggest following the cookiecutter template and examples as is. The cookiecutter, although it leverages the To answer your question, keep it in the provider module. As for the second part, you can name your variables in any way you prefer. The most important thing is that the entry point is correctly declared in the toml. |
Thanks for the quick response :). I will keep it in the cookie-cutter template form. To get back to the initial issue at hand: I have fixed the error by leaving the object's variable name as Wouldn't [tool.poetry.plugins."openbb_provider_extension"]
openbb_orats = "openbb_orats.provider:orats_provider" be the correct entry point to the provider module and the object variable orats_provider = Provider() ,as stated above? |
That should be the case and should work. Make sure to pip install again so it picks up the changes in the |
@jjfantini heads up that I pushed a uvicorn fix that slightly changes the import statement. Now it is |
I am building an openbb extension with the openbb-cookiecutter template.
When I run:
I get the error:
The CONTRIBUTING GUIDELINES explain that I should put the provider in the
__init__.py
file, but the cookiecutter template adds a whole modules for this.Should I put the provider in the
__init__.py
file or should I keep the provider module?EXTRA INFO:
When I run:
This executes without issue. Any help would be appreciated!
The text was updated successfully, but these errors were encountered: