8000 Adding docs about fallback parameters by helio-frota · Pull Request #460 · nodeshift/opossum · GitHub
[go: up one dir, main page]

Skip to content

Adding docs about fallback parameters #460

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

Merged
merged 1 commit into from
Sep 11, 2020
Merged

Adding docs about fallback parameters #460

merged 1 commit into from
Sep 11, 2020

Conversation

helio-frota
Copy link
Member

Related to #459

@lance @lholmquist I'm not 100% sure if we need to run npm run build:docs before to send the PR when updating the docs.

Copy link
Member
@lance lance left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@helio-frota - yes, if you are updating docs, npm run build is needed. The site is published from the master branch in the /docs directory.

README.md Outdated
@@ -76,6 +76,21 @@ the `open` state.
When a fallback function is triggered, it's considered a failure, and the
fallback function will continue to be executed until the breaker is closed.

Also the fallback function accepts the same parameters as the fire function:
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nit:

Suggested change
Also the fallback function accepts the same parameters as the fire function:
The fallback function accepts the same parameters as the fire function:

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you. PR updated 👍

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I believe when we do a release, the docs are updated as part of that npm script, so that should take care of it. I've created an issue for trying to automate the doc creation also, #461

We could also see about using release-please for doing releases, similar to what we are about to do on the js cloudevents SDK library, cloudevents/sdk-javascript#329

Copy link
Member
@lholmquist lholmquist left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

Regarding having to generate the docs, i wonder if we should start using a GH action to generate them on merges to master?

@lholmquist lholmquist merged commit e8989b6 into master Sep 11, 2020
@helio-frota helio-frota deleted the docs branch September 11, 2020 16:30
@helio-frota helio-frota self-assigned this Dec 21, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants
0