Thank you, all. I've created
https://issues.apache.org/jira/browse/OFBIZ-11902 to track this.
Best,
Girish
On Tue, Jul 21, 2020 at 1:14 AM Jacques Le Roux <
jacques.le.r...@les7arts.com> wrote:
> Thanks Mridul,
>
> I agree about enhancing existing service definitions
>
> Jacques
>
> Le
Thanks Mridul,
I agree about enhancing existing service definitions
Jacques
Le 20/07/2020 à 10:37, Mridul Pathak a écrit :
Hi Girish,
I think this would be a good improvement to service definition. While it makes
more sense that it would enable creating JSON like schema definitions it would
Hi Girish,
I think this would be a good improvement to service definition. While it makes
more sense that it would enable creating JSON like schema definitions it would
make service definitions more predictable in general. This improvement could
also be applied to existing service definitions
Hi Girish,
I don't remember this having been discussed before. I like the idea and the proposed
"implementation".
I don't think it's a too big change, it's an improvement for me.
About Pritam's remark for GenericValue, if it may help: those are Maps
[Map] and considered as such in SOAP.
Hello Girish,
IMO, the option which you have suggested looks good in case if we want to
leverage upon the existing service definitions for creating the API
documentation. I also think that this could be a good addition to OFBiz in
the developer perspective, as right now, it is very difficult to
Hey Guys,
While working on OpenApi integration as well as GraphQL implementation, I
faced issues on how to automatically document request/response JSON
structure for service attributes that were of Collection types (Map, List
etc).
For simple types, it is just plain easy but when it comes to
