Skip to content
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

Missing symbolicEqual from _types/index.d.ts_ #2960

Closed
wlewis-formative opened this issue May 31, 2023 · 10 comments · Fixed by #3035
Closed

Missing symbolicEqual from _types/index.d.ts_ #2960

wlewis-formative opened this issue May 31, 2023 · 10 comments · Fixed by #3035

Comments

@wlewis-formative
Copy link

Should symbolicEqual also appear in this file?

If this looks correct, I can open a PR with the changes:

diff --git a/types/index.d.ts b/types/index.d.ts
index 67b9d09aa..fd05af220 100644
--- a/types/index.d.ts
+++ b/types/index.d.ts
@@ -973,6 +973,21 @@ declare namespace math {
     ): MathNode
     simplifyCore(expr: MathNode | string, options?: SimplifyOptions): MathNode
 
+    /**
+     * Determines if two expressions are symbolically equal, i.e. one is the
+     * result of valid algebraic manipulations on the other.
+     * @param {Node|string} expr1 The first expression to compare
+     * @param {Node|string} expr2 The second expression to compare
+     * @param {Object} [options] Optional option object, passed to simplify
+     * @returns {boolean} Returns true if a valid manipulation making the
+     * expressions equal is found.
+     */
+    symbolicEqual(
+      expr1: MathNode | string,
+      expr2: MathNode | string,
+      options?: SimplifyOptions
+    ): boolean;
+
     /**
      *  Replaces variable nodes with their scoped values
      * @param node Tree to replace variable nodes in
@josdejong
Copy link
Owner

Thanks for reporting, the function symbolicEqual should indeed be added to the TypeScript definitions. Anyone able to help out here?

@juancodeaudio
Copy link
Contributor

Hi, can I take this issue?

@josdejong
Copy link
Owner

Yes, thanks Juan!

@Uj293
Copy link

Uj293 commented Oct 3, 2023

Is this issue resolved or not ..??

@josdejong
Copy link
Owner

@Uj293 there is a PR to fix this, but it is not yet merged or published. It's awaiting feedback from @juancodeaudio .

@Uj293
Copy link

Uj293 commented Oct 4, 2023

@josdejong so i can start working on this too if you assign this one to me

@josdejong
Copy link
Owner

Thanks, that would be great. Let's await for a day or so to see if Juan replies, if not, I hope he will not mind if you take his PR and finish it.

@josdejong
Copy link
Owner

@Uj293 we didn't yet hear back from Juan. Can you take over his PR? Thanks!

@josdejong
Copy link
Owner

The types have been fixed now in in v11.12.0, fixed via #3035.

@wlewis-formative
Copy link
Author

Thanks everyone!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants