-
Notifications
You must be signed in to change notification settings - Fork 83
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
Make calculator functional #83
Comments
I'll be working on this myself, though if you got any suggestions, comment here. And if you wish to contribute, comment here, and while making the PR, choose |
I'll not be working on this. If you wish to volunteer, you'll have my gratitude |
I can take it |
Thanks. Please take a look at the naming conventions, try not too include any extra library if you can help it, and overall, just make it good. Will be waiting for your PR :) |
Great!
In UPDATE: import { Rnd } from 'react-rnd'; and its usage the problem solved |
Uhh yeah, I recommend you make your own branch and start over, that one has issues |
Its related to Vite's version. Its fixed in main branch. Make a branch off of main anf start, nothing much in function-calculator brqnch anyway |
Alright, Thanks :) |
It's still an issue - when pressing one of the apps in the bottom toolbar - I cannot open it and see this error in the console |
@PuruVJ |
Uhh yeah, its because I have package-lock.json as lock file(we're using npm here), so yarn might be skipping it. Try using npm, and if you can't, install [email protected] exact. That fixes the problem |
Thanks - it works, I installed it with npm 👍 |
Still WIP - I did not know that calculator logic contains so many edge cases. |
That is great! I love the fact you're still at it after so long! 🤗 Using TDD here feels like a great way going forward. Document the functionality, and use it as a map going forward!! Kudos! Looked at the code, and it looks great to me. Would be happy to merge when it is complete 👌 |
Calculator, currently is non-function. Make it function:
The text was updated successfully, but these errors were encountered: