@varon yeah, should probably write one to solr community :) https://cwiki.apache.org/confluence/display/solr/Uploading+Data+with+Index+Handlers#UploadingDatawithIndexHandlers-Solr-StyleJSON
I guess I made a misstake choosing json out of familiality in the first place. should probably use xml
Failing that, can you not just send individual commands, etc?
Let's not ask about why they're using JSON commands in the first place for an HTTP API. Didn't RPC die years ago?
shouldn't it be in the chiron channel?
as for "valideness", I didn't think about it initially but it looks like the answer is not that simple https://stackoverflow.com/questions/21832701/does-json-syntax-allow-duplicate-keys-in-an-object
sorry, I followed the link here from Chiron site. do we have a dedicated channel for chiron?
could probably PR in a link fix, it's likely copied from the aether page.
use Chiron*
I have a Core project that contains my "domain" types, and I can't have it reference Chiron since it needs to also compile to JS via Fable
I want to use Chiron to define mapping from these domain types to JSON, but the mapping needs to be defined in a separate server-only assembly
hi guys, I recently came to Chiron and I love it! I found that I can use function
serializeWith and pass it custom mapping function instead of having static member ToJson, which is great. But there is no deserializeWith? Did anyone know why is it missing? I suppose it is by design so I am just curious, what is the internal reason? :)
parsed |> myDeserialize
and there is a chiron dedicated channel ;)
does anyone have any clever ideas about making lenses out of record types automatically? say with a type provider?. I don't know enough about type providers but it would be cool to do things like
type MyRecord = { property : string}
....
MyRecord.property_ : Lens<MyRecord,string>This can be declared simply enough with
module MyRecord =
let property_ : Lens<MyRecord,string> = (fun s -> s.property),(fun v s -> {s with property = v})But that always looks the same for every property, so would be neat if it could be automatic :)
@btrepp - There's an RFC for expanding the capabilities of type proviers, currently in early proof-of-concept stage. Making lenses from record types automatically via a type provider was one of the use cases mentioned. Keep an eye on that one, and contribute if you're able to so that it gets completed faster, and that should be what you're looking for here.
Could someone suggest a good example for working with nested jsons with chiron?
So my first intro to lenses was aether, and I'm not too around the theory, but we have prism defined as
Prism<'a,'b>: ('a->'b option),('a->'b->'a). I can somewhat intuit that, but sometimes I feel like I want to reach for something of the form Prism<'a,'b>: ('a-> Result<'b,string>),('a->'b->'a)
With the idea that the Prism ultimatelty tells us which part in the tree is missing
So when one goes Optic.get lens data we get
Result<'a,string> with an error message about why the lens failed. (Which would be handy in logging)
Am I insane/missing the point?
What are you trying to achieve by discovering where the None started in the chain?
May be slightly nicer to have the
TError be a string list instead, that gets the chain appended too.
At the moment I find myself writing a would bunch of Result<'a,'b> code after I get specific parts of objects
I'm looking at https://xyncro.tech/aether/guides/lenses.html
deeper'