-
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
feat: Use new sdk instructions instead of hello READMEs #152
feat: Use new sdk instructions instead of hello READMEs #152
Conversation
|
||
# Create a helper function for rendering messages. | ||
def show_message(s): | ||
print("*** {}".format(s)) |
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.
return errMsg{err: err} | ||
} | ||
|
||
return fetchedSDKInstructions{instructions: content} |
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.
despite the name of the function we're still sending fetchedSDKInstructions
message type - figured we can update either the message name or the function name when we stop fetching from the READMEs but this way we can still just handle this one message in the showSDKInstructionsModel.Update
method.
# Set up your application | ||
|
||
If you want to skip ahead, the final code is available in our [GitHub repository](https://github.com/launchdarkly/hello-python). | ||
|
||
|
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.
I think maybe when the instructions are all in we might want to pull this intro text out of the markdown file/viewport box
Copies the instructions from the guided quickstart here as markdown files to render in the setup flow. Starting with just one SDK (python) to establish the pattern.