This PR standardizes the example folders across our repos. It includes the following changes:
Adds a README to introduce the example.
Edits the example code comments to include a bit more information and use the same wording as I've proposed in the other repos.
Slightly simplifies the code, per Andi's request. Note: I left in the function to set the secret to the env variable, because I think it's nice to have a grounded example of how to do something with the secret. If you want to change this to a function that prints the secret, like the other repos' examples, I think that would work too.
Closes #54
Questions:
Is there any other information we should include in the README? For example, the JS example readme includes a command to run the JS examples.
Should we call the folder "examples" like we do for JS, or do we anticipate only having a single example here?
Should we change the function to have it print the secret like the examples in the other repos?
This PR standardizes the example folders across our repos. It includes the following changes:
Closes #54
Questions: