-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add feature for Serde #8
base: master
Are you sure you want to change the base?
Conversation
You're serializing the whole object? Those can get quite large with all of the file lists, which most people don't even care about |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@lleyton Could you describe a bit about your use case?
Yeah, in my use case, I'm serializing all of the packages within several repos to JSON in order to load them into a mellisearch index. My plan is to use this index for a web app which allows full-text package search (descriptions, names, author, etc..). |
Ok. You're sure you'll want everything and not a more restricted set of fields? |
Hmm, it's likely that I'll want a more restricted set of fields when I'm further along. For prototyping though, I'm using all of them for now. |
I'm a little hesitant to merge this unless if it's not exactly what is needed. Would you mind if I waited to merge and release this until you are mostly done with your prototype? |
Sounds good with me :) |
It's useful if you need to store the repo metadata into a different format. In our case, we're using it serialize it as JSON for Mellisearch.