Daniel Beskin

I can try both... I'll use Play for the example, but it's problematic for all other formats as well. Given this code: ```scala import io.fintrospect.formats.Play.Auto._ val js: JsValue = ???...

In the specific use-case I have it's complicated to initialize a valid value (there are a number of nested collection values there, and it just adds noise in the code)....

I'll try looking into it when tackling #41, though since I'm new to the library, I'm not sure what I'll come up with...

Thanks for the suggestion. Although I'm definitely in favor of generating randomized data (be it for tests or for the schema examples), sadly, our codebase is not there yet, it'll...

I didn't want to add more code to `Zipper` as it is already quite bloated. This way, more axes can be added in the future without touching the `Zipper` implementation.

You're probably right about all the problems related to pimping, but it just feels nice to compose things that way and seems all so harmless... I think it's a bit...

I will try to add a children axes to the ones currently implemented, shouldn't be too difficult. I couldn't figure out a way to make axes equivalent to selection and...

In the presence of tree modifications, `ancestor` does not replace `unselect`. In general, shifting the zipper only shows direct modifications of nodes, it doesn't do the merging step (this would...

As far as I can see there, in case of tree modifications, there is no way to avoid `unselect`. Ignoring tree modifications, it may be possible to add axes directly...

My bad, @josharnold52's code I was looking for, was in my inbox. Here's the relevant code: ``` scala trait PathFunction { def apply(g: Group): Zipper def directChildren: PathFunction def allChildren:...