-
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
JSON comparison is too complex #25
Comments
@h1alexbel thank you for reporting this. I'll assign someone to take care of it soon. |
@h1alexbel this is your task now, please go ahead. Deadline (when this ticket should be closed) is Estimation here is Remember, you don't have to solve everything in this ticket - you can solve it partially and leave If you have any questions don't ask me, I'm not a technical person. Open new tickets instead. If you don't have time or simply don't want to work on this, you can always resign. |
@h1alexbel Don't forget to close this ticket before the deadline (2023-07-03T14:09:05). You are past the first half of the allowed period. |
@h1alexbel Looks like you've missed the task deadline (2023-07-03T14:09:05). You are now resigned from this task. Please stop working on it, you will not be paid. I will assign it to someone else soon. |
@h1alexbel I couldn't find any assignee for this task. This is either because there are no contributors with role Please, make sure there is at least one available contributor with the required role and the project can afford to pay them. |
1 similar comment
@h1alexbel I couldn't find any assignee for this task. This is either because there are no contributors with role Please, make sure there is at least one available contributor with the required role and the project can afford to pay them. |
we have so many methods to validate JSON equality, we need to stick to the only one of them
The text was updated successfully, but these errors were encountered: