-
-
Notifications
You must be signed in to change notification settings - Fork 27
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 use ramhorns with serde_json::Value? #44
Comments
Ramhorns supports This should be a good first issue if anyone wants to drop a PR, I might not have time to tackle this within the next week or two. |
I will try implementing Content trait for |
If |
Just put the #[cfg(feature = "json")]
mod serde; Adding [dependencies]
# ...all the other deps
serde_json = { version = "1.0", optional = true }
[features]
default = []
# Implements `Content` for `serde_json::Value`
json = ["serde_json"] That way enabling the |
I think I might be hitting this as well. But to make sure - there is no alternative means of using arbitary json (even if say, converted to some string type) with a template and ramhorns today, correct? I've been unsuccessful anyways. If that is the case then I'm a huge 👍 on this feature request and I would be curious to know if there has been any progress on the feature! |
@eeyun don't think there has been, happy to accept a PR. |
Cool I just wanted to make sure. It would be a great feature. I may try to get something together for it but a bit underwater currently. Thanks for maintaining the project either way! |
I'd like to be able to use ramhorns with arbitrary data supplied via JSON. From what I can tell,
serde_json::Value
fits the requirement for doing this but ramhorns uses a derive trait which won't work with serde_json::Value because it's an enum.Is there a workaround or an easier way to accomplish using arbitrary data with ramhorns that doesn't require using the
ramhorns::Content
trait?The text was updated successfully, but these errors were encountered: