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

How to keep schema._typeid's equality between client side and server side #89

Open
zgz682000 opened this issue Aug 13, 2020 · 2 comments

Comments

@zgz682000
Copy link

As my code reading, to keep schema._typeid's equality, server side and client side must import schema class in the same order. If so, it's hard to maintain.

@endel
Copy link
Member

endel commented Aug 13, 2020

Hi @zgz682000, I agree. Have you faced this issue yourself or you're pointing out a potential problem?

@zgz682000
Copy link
Author

I faced, and had to move all schema classes into one single file, so that client and server are able to share this file.

May be, custom assignable typeid would be a better way.

😊😊

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