-
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
python-sdk documentation update #27
Conversation
docs/source/jupyter/sdk.ipynb
Outdated
"class MyMarketPlaceApp(MarketPlaceApp):\n", | ||
" def heartbeat(self) -> str:\n", | ||
"from marketplace.app.v0 import MarketPlaceApp\r\n", | ||
"class MyMarketPlaceApp(MarketPlaceApp):\r\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Still not sure whether this is a good idea, but then we probably have to provide some kind of app_type
parameter or so to the get_app()
function.
3f3248c
to
c86cf93
Compare
for more information, see https://pre-commit.ci
docs/source/jupyter/sdk.ipynb
Outdated
"In order to easily and effectively communicate with a registered application in MarketPlace via Python, the Python Software Development Kit (SDK) can be used. Follow the instructions on the [application registration](../apps/registration.md) page to register an application with MarketPlace. Once the application is registered, you will find the `client_id` in the registration output.\n", | ||
"\n", | ||
"# MarketPlace SDK\r\n", | ||
"\r\n", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It seems like this PR is introducing mixed line endings (\r\n
vs \n
). I thought that the mixed-line-ending
pre-commit hook should fix that, but it does not seem to be the case. Can you briefly look into that?
Co-authored-by: Carl Simon Adorf <[email protected]>
for more information, see https://pre-commit.ci
Co-authored-by: Carl Simon Adorf <[email protected]>
Addressing #26