-
-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[bug] the Monitor class not correctly initialize #4672
Comments
In fact I think we should not solve problems like this one-by-one. There should be another layer like factory function to receive all return value of Or find a way to convert tagged rust trait method into JS class method. Which looks not easy, and needs to consider about much of edge cases and constraints. |
I think it'll be easier to manage this in the function itself, converting the JSON object to the correct class. |
@lucasfernog but how to map a JSON object to the correct class? create a wrapper json object with the origin object and a class name identifier? |
The class interface should be adapted for each case. Same as #2621 we need to map the size and position fields of the Monitor to its classes. |
@lucasfernog I am not sure if I totally understand your opinion, but if you mean to use the same solution as #2621 to solve this problem, I will happy to try to handle this. |
Describe the bug
I have searched and read #2599 and #2621, and I think if we return a
Monitor
instance here:this problem might be solved.
Reproduction
No response
Expected behavior
No response
Platform and versions
Stack trace
No response
Additional context
No response
The text was updated successfully, but these errors were encountered: