how to expose types that are mostly just a wrapper around a collection

[rajkosto]

i have some types that are just a wrapper around vector, map, etc
i thought just passing through cbegin/cend/begin/end/at/operator[] key_type and value_type would be enough but it doesn't seem to be
the internal collection member is private so i can't just passthrough that one via a lambda

[rajkosto]

im now trying to get unknown_read/unknown_write to just read/dump values from the "self" object but lambdas arent supported for those, only member function and object pointers...

[stephenberry]

What kind of wrapper is this? Consider how the wrapper's purpose should be seen in JSON. For example, std::optional is a wrapper that provides a null state.

Lambdas are allowed for self and for glz::custom, so there's probably just a misunderstanding.

Can you provide a simple code example of what your wrapper is like and what its purpose is? Take a look at glz::custom as well, where you can register lambdas for decode/encode.

[rajkosto]

I actually tried just exposing the inside vector but I kept getting strange errors I couldn't fix like mangled_name not defined (which I couldn't fix even by adding "name" to meta for the inner key/collection type, I think it's because those types were templates ?)
And how would one use custom to have a key/value style output when the collection is an array or vector instead of a map?

[stephenberry]

mangled_name not being defined could come from your type not being reflectable (aggregate initializable). It is hard to say without any code or error output.

Use array() rather than object() in your glz::meta to deal with a collection that should be an array instead of a map (object).

[stephenberry]

I've converted this to a discussion until more information can be given.