Open st-Wook opened 2 months ago
This is a known limitation, and it's mentioned in the createBinarySerializer
documentation.
Changing this behavior in Flamework would likely be the easiest solution as it's otherwise non-trivial to sort the various types.
Ah, I see... Thank you for the explanation!
I am experiencing an issue with the @rbxts/flamework-binary-serializer@0.6.0 package. Here is my code:
When compiled, the output occasionally differs as shown below:
When the incorrect case is compiled, I encounter the following error:
Additionally, the packed object type definitions are shared and used in multiple places. The same type is used across different createBinarySerializer calls. However, during serialization and deserialization, the formats differ, causing the error. Could you modify the compilation process to ensure that the same type always compiles to the same format?