justincui opened a new issue, #1727:
URL: https://github.com/apache/fury/issues/1727

   ## Is your feature request related to a problem? Please describe.
   <!-- A clear and concise description of what the problem is. Ex. I'm always 
frustrated when [...] -->
   I'm always frustrated when debugging serialized data because it's difficult 
to visualize the binary structure. Understanding the detailed binary layout and 
content of serialized bytes would greatly enhance debugging and development 
efficiency.
   
   ## Describe the solution you'd like
   <!-- A clear and concise description of what you want to happen. -->
   I would like a feature in the Fury debugtool component that can parse 
serialized bytes and display their binary structure in a human-readable YAML 
format (with depth control as a parameter). Additionally, the ability to 
convert the YAML representation back into the original binary format would be 
extremely helpful for verifying and testing changes during debugging. This 
bidirectional functionality would provide a robust tool for developers to work 
seamlessly with serialized data.
   
   ## Additional context
   <!-- Add any other context or screenshots about the feature request here. -->
   Implementing this feature would bridge the gap between serialized data and 
its human-readable representation, making it easier to inspect, debug, and 
validate serialized objects. It would be particularly useful for developers 
working with complex data serialization and deserialization processes, enabling 
them to make changes in YAML and convert them back to binary for testing 
purposes.
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to