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

guidance on marshaling/unmarshaling #176

Open
richardhenwood opened this issue May 16, 2024 · 0 comments
Open

guidance on marshaling/unmarshaling #176

richardhenwood opened this issue May 16, 2024 · 0 comments

Comments

@richardhenwood
Copy link

hi,

I would like to wrap this graph library in a api so I can interact with it from a web page. I have got a basic graph built with my custom vertex type. i have a Fiber route and provides access to my basic graph . When I attempt to marshal the graph to JSON in Fiber, I get an empty string.

To my inexperienced eye, it looks like I should use the Store interface. I should store the graph somewhere (like memory?) and then marshal/unmarshal the stored graph. Does that sound like the right/best approach?

thanks,
richard

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

1 participant