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

Type mismatch in comparison #71

Open
anirudhbh2004 opened this issue Apr 16, 2018 · 1 comment
Open

Type mismatch in comparison #71

anirudhbh2004 opened this issue Apr 16, 2018 · 1 comment

Comments

@anirudhbh2004
Copy link

Is it possible to add an enum for type mismatch as well?

In one of my use case, the value at a particular JSON patch was same but one was of type string and other was of type long and I wasn't able to figure out the reason for failure.

@LouizFC
Copy link
Collaborator

LouizFC commented Apr 16, 2018

@anirudhbh2004 Hi.

I have a plan to release a feature that might help you, you can see more here #63 (comment).

I please ask you to read through the comment and see if it can solve your problem.

Other thing that might be of use is implementing some predefined "Modes". Some examples would be:

  • Default
    the way we handle things now
  • Numeric Equivalence
    to solve the original problem that I was trying to solve
  • Strict Typing
    to solve your issue
  • Custom
    so people can implement their own rules

Implementing it might be quite simple, but I am at a very busy moment of my life right now, I am sorry.

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

No branches or pull requests

2 participants