percivalalb
percivalalb
Address most of the bullet points. Where is the best place for the example? Edit: Added an example to the READMD.md
I don't believe so. The issue at play here is that only fixed fixed components are generated as concrete go struct (fine) and used if they are referenced by the...
Same issue with the GET endpoint: https://wit.ai/docs/http/20221114/#get__entities__entity_link
This looks to have been resolved in v2.1.0 of the Go client library: Compare https://pkg.go.dev/github.com/wit-ai/wit-go/[email protected]#Entity vs https://pkg.go.dev/github.com/wit-ai/wit-go/[email protected]#CreateEntityResponse However the docs still look wrong: 
Go client was fixed by https://github.com/wit-ai/wit-go/pull/30 and mentioned in https://github.com/wit-ai/wit-go/issues/23
The minimal-spec in https://github.com/percivalalb/kin-openapi/commit/04d5174c70427898aad888140ecb25fc244e215b shows the issue: - Firstly note there is only one schema component `record` in the internalised spec which both of the endpoints reference, even though they...
I've started implementing a solution which improves the naming of internalized refs, it works ^TM . Needs some tidying up and iterating on but it fixes the issues seen upstream...
> Changes between the two releases: https://github.com/getkin/kin-openapi/compare/v0.118.0...v0.120.0 I've not confirmed but I believe it's been an issue since the internalise ref functionally was added to kin-openapi given the comment: https://github.com/getkin/kin-openapi/blob/f170f8ca2ea9265ce85da309c23e5f97e3e47643/openapi3/internalize_refs.go#L383-L386
Oh, you can parse them if you provide the number with the leading 0 from the national format or provide the region. ```console $ perl -Ilib -Mv5.16 -MNumber::Phone::Lib -e 'my...
Found this: https://github.com/DrHyde/perl-modules-Number-Phone/blob/251a4c2342f42cb20784b0c944a031c157bdefc8/t/number-phone-country.t#L164 https://github.com/DrHyde/perl-modules-Number-Phone/blob/251a4c2342f42cb20784b0c944a031c157bdefc8/build-data.country-mapping#L159 My guess would be because there is a special case to return the country as GB, this messes up the ability to actually parses the number...