-
Notifications
You must be signed in to change notification settings - Fork 32
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 proper checks for input format #50
Comments
I would like to work on this issue under GSSOC`22. Please assign it to me. |
Thanks. I am working on it. |
I would like to work on this issue under GSSOC'22. Please assign it to me. |
@Gurdeep475 Your status? |
working on it. |
@adityabisoi how should I give an error, like should I create an alert that displays an invalid expression message or simply throw the error? |
Show it to the user. |
@Gurdeep475 Updates on this issue? |
@adityabisoi yes, most of the work is done, just working on one remaining algo. |
@adityabisoi need some guidance here, I have got the algorithms for validating prefix notation but am not able to get the same for infix and postfix ones. |
I would like to work on this issue under GSSOC`22. Please assign it to me. |
@SonakshiGoyal I shall assign this issue to you if @Gurdeep475 doesn't make a PR until tomorrow. |
This issue is now open to contributions. |
@adityabisoi I would like to work on this issue in GSSOC'22. |
Add checks to ensure the input format is correct for each operation
Ex: infix input if entered in a postfix-infix transition, must give out an error.
The text was updated successfully, but these errors were encountered: