-
-
Notifications
You must be signed in to change notification settings - Fork 0
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/v2 #157
Conversation
Codecov Report
@@ Coverage Diff @@
## master #157 +/- ##
===========================================
- Coverage 100.00% 97.43% -2.57%
===========================================
Files 9 11 +2
Lines 136 195 +59
Branches 27 69 +42
===========================================
+ Hits 136 190 +54
- Misses 0 5 +5
Continue to review full report at Codecov.
|
im not fully happy with how the math parser works, but this is in-spec with how jagtag does it, assuming its only for doing actual arithmetic
- do math in the proper order of operations - when math is supplied with non-ints, do string manipulation
Resolves #84 |
this is exactly how original jagtag does it, its even still pemdas compliant!
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.
A few styling nits. Moreover:
- There are currently some significant gaps in code coverage, mainly related around error conditions. These should be covered.
- Unnecessary explicit variable type declarations can be removed to reduce noise.
- The removal of the mandate to use strict boolean expressions can be enacted to reduce a lot of noise around boolean checks. This should in my opinion be done to allow JS truthy/falsy logic to be taken advantage of.
Co-authored-by: Linus Willner <[email protected]>
This rewrites the module to pure Typescript, and also fixes some spec violations along the way.