-
Notifications
You must be signed in to change notification settings - Fork 8
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
Update lib.rs and added few more punctuation marks #13
Update lib.rs and added few more punctuation marks #13
Conversation
Thank you for the pull request!The Scribe team will do our best to address your contribution as soon as we can. The following is a checklist for maintainers to make sure this process goes as well as possible. Feel free to address the points below yourself in further commits if you realize that actions are needed :) If you're not already a member of our public Matrix community, please consider joining! We'd suggest using Element as your Matrix client, and definitely join the General and Desktop rooms once you're in. Also consider joining our bi-weekly Saturday dev syncs. It'd be great to have you! Maintainer checklist
|
Hey @RyanPaulGannon, would you have a moment to do an initial review here? :) |
Hey @KesharwaniArpita! Thanks for the PR, there's a few lines here that aren't compiling but it's because it's not part of the If you take a look at this link, you'll be able to correct the lines and resubmit :) If you need any help, give me a shout! |
Please review comments and refer to the rdev crate please. There are still a few variants used that aren't included in the enum which is causing the program to not complie. Please run:
before committing so you can check to see that the program works first :) |
@RyanPaulGannon I am so sorry for the inconvenience. That surely wasn't the intention. It should work fine now.
I keep on getting the following error and I can't figure out what is causing them. Is there anything missing in the |
Don't worry at all, the PR is looking great now - thank you! Thank you for highlighting this as we'll need to add it to the |
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.
Looking good, I'm happy that this satisfies #11! Eventually, there will need more work doing regarding punctuation, however, it'll be done alongside implementing the Shift
key to allow for capitalisation and general shifting of keys.
Nice I'll check the docs to make sure the notes on Cargo are explicit (enough) :) |
If you would like me to make the PR for it, I can do - just let me know, I know you're a busy man! |
Ya that actually would be really nice, @RyanPaulGannon :) Thank you! |
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.
Thanks for the contribution, @KesharwaniArpita, and also for the review, @RyanPaulGannon! 🚀
Contributor checklist
Description
This pull request enhances the allowed_keys function by adding support for a comprehensive set of punctuation marks and special characters. The function previously handled only a limited selection of punctuation, such as commas and semicolons. This update improves the coverage of punctuation, allowing the function to return characters like apostrophes, periods, exclamation marks, and more.
Related issue