Exposing ZogSchema

[pcfreak30]

This may likely be a breaking change but no external schema can be created by using any existing as a template. Im aware this is being though about in other approaches but we currently cannot implement ZogSchema/ComplexSchema

Cannot use (*StatusSliceSchema)(nil) (type *StatusSliceSchema) as the type zog.ZogSchema
Type cannot implement zog.ZogSchema as it has a non-exported method and is defined in a different package

type ZogSchema interface {
	process(ctx *p.SchemaCtx)
	validate(ctx *p.SchemaCtx)
	getType() zconst.ZogType
	setCoercer(c CoercerFunc)
}

This prevents advanced use cases...

[Oudwins]

Hey! Yes I'm aware. But I don't want to expose these methods on the default schemas. Ideally I would like to have some way to flag to users that these are internal methods but export them (like we do in js with object._privateishMethod(). Unfortunately this is not possible in Go.

So the API for this will be

z.Use(customSchema)
// Real example is that you might import these schemas from another package and do

z.Struct(z.Shape{
 "Coin": z.Use(coins.Coin().Min(0).Max(100))
})

I haven't released yet because I'm working on the codegen stuff and that might change the interface that z.Use uses. But if you have a usecase where and would like to build custom schema I'm happy to release the current implementation under some kind of horrible interface name (i.e EXPERIMENTAL_ZOG_PUBLIC_SCHEMA) and ship z.Use for you to try.

[pcfreak30]

Hey! Yes I'm aware. But I don't want to expose these methods on the default schemas. Ideally I would like to have some way to flag to users that these are internal methods but export them (like we do in js with object._privateishMethod(). Unfortunately this is not possible in Go.

So the API for this will be

z.Use(customSchema)
// Real example is that you might import these schemas from another package and do

z.Struct(z.Shape{
"Coin": z.Use(coins.Coin().Min(0).Max(100))
})
I haven't released yet because I'm working on the codegen stuff and that might change the interface that z.Use uses. But if you have a usecase where and would like to build custom schema I'm happy to release the current implementation under some kind of horrible interface name (i.e EXPERIMENTAL_ZOG_PUBLIC_SCHEMA) and ship z.Use for you to try.

use case is due to #185 I kind of have to define a completely custom type if i want zog to handle a custom typed slice and do string manipulation on it.

[Oudwins]

Yea I figured. I'm happy to ship the custom schema stuff if you would like to try it. This PR adds functionality for this #187