-
Notifications
You must be signed in to change notification settings - Fork 757
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: "StarkNet" to "Starknet" #723
feat: "StarkNet" to "Starknet" #723
Conversation
✅ Deploy Preview for starknetjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
@janek26 @dhruvkelawala @yoga-braavos can you please give your input about this? 🙏 |
relevant: |
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.
lgtm
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.
Leaving a "request changes" so this doesn't get merged yet, I'll prune some of the doc changes beforehand.
Done.
c11f166
to
9a2e0e0
Compare
✅ Deploy Preview for starknetjs ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
This should be combined with off-chain signing PR |
927846e
to
800091e
Compare
800091e
to
c9a81bb
Compare
🎉 This PR is included in version 6.0.0-beta.14 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This PR is included in version 6.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
🎉 This issue has been resolved in version 7.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Motivation and Resolution
Because the official name is "Starknet", remove all instances of "StarkNet" in favour of "Starknet".
Issue: #705
Usage related changes
Development related changes
Checklist: