Skip to content
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

Add dynamic text and label properties for buttons #1815

Merged
merged 4 commits into from
Feb 25, 2022

Conversation

radibit
Copy link
Contributor

@radibit radibit commented Feb 18, 2022

Hey folks 👋

This PR:

  • adds dynamic text and label properties for the button component
  • avoids duplicate code for the button component (getConfigOption function)
  • updates the button unit tests
  • updates StepOptionsButton interface
  • updates usage docs with the new info about the button component

The common case for dynamic text and label button properties is when Shepherd is used with an i18n (internationalization) solution and those fields need to be updated on change of the language settings. That has been already in place for the main text component but was missing for the buttons.

@RobbieTheWagner
Copy link
Member

Hi @radibit, thanks for the PR! This is definitely a useful feature. Would you mind also updating the docs to mention these things can now be functions and how to use them, etc?

@radibit
Copy link
Contributor Author

radibit commented Feb 18, 2022

@rwwagner90 Thank you for the quick response. I'll update the docs, good reminder 👍

Copy link
Member

@RobbieTheWagner RobbieTheWagner left a comment

Choose a reason for hiding this comment

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

This looks good! Thanks for making those changes and thanks for the PR.

@RobbieTheWagner RobbieTheWagner merged commit cb67f24 into shipshapecode:master Feb 25, 2022
@radibit
Copy link
Contributor Author

radibit commented Apr 6, 2022

Hey @rwwagner90 sorry to bother you but can I ask if there is a release in planning for the next version of Shepherd library which will include the change completed with this PR?

ℹ️ Unfortunately, there isn't a way to point in my package.json to the base (master) branch of Shepherd since the distribution step is part of the npm publishing process.

@RobbieTheWagner
Copy link
Member

@radibit I released the other day. Sorry for the delay!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants