-
Notifications
You must be signed in to change notification settings - Fork 20
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
docs: add a guide to test changes locally #866
docs: add a guide to test changes locally #866
Conversation
Quality Gate passedIssues Measures |
This pull request is automatically being deployed by Amplify Hosting (learn more). |
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.
Geat explanation, well done!
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.
Nice addition, thanks a lot @NOMADE55 !
37f38ee
into
scania-digital-design-system:develop
@@ -23,6 +23,22 @@ | |||
## Style Guides | |||
- **Code Style**: Please read our [Code Style](/~https://github.com/scania-digital-design-system/tegel/blob/main/CODE_STYLE.md) before contributing. | |||
|
|||
## Testing your changes locally | |||
To properly test your changes' behaviors in a project, reference your local Tegel instance instead of the published version on the registry |
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.
To properly test your changes' behaviors in a project, reference your local Tegel instance instead of the published version on the registry | |
To properly test your changes in a project, reference your local Tegel instance instead of the published version on the registry |
Glad to help! |
Describe pull-request
Adds a short but sweet guide to play locally with changes made to the Tegel Design System. helping future contributors test behaviors thoroughly.
Issue Linking:
Checklist before submission
npm run build-all
without errorsAdditional context
Keeping my word #861