ZepHakase
ZepHakase
@mneethiraj - It was exactly what I did but it works only for > GET / typedefs? serviceype = {servicetype} how you can see here in the code. But if...
@mneethiraj -In my opinion you are right because I can't understand why we have a cache for the name, a cache for the guid and now also a cache for...
@mneethiraj - I looked more closely at the code and we could: 1) limit the rest api for the four types one for the post, one for the put, one...
@mneethiraj - I didn't understand if you propose to add new REST APIs by type /enumdef /servicetype/hive for example) but use the /typedefs code like /typedefs?serviceType=hive&&type=enum or not to add...
@mneethiraj - Regarding the DELETE you are proposing the fact of not implementing it for the serviceType because moving the work on the client only works if you use the...
I agree absolutely. I don't want to create a complex Rest system to access however the customer wants. I only think that access by service type is much more useful...
@mneethiraj - any way the ATLAS-3180 pull request does exactly what you say.
Thx, so much. I think it is appropriate to eliminate this "confusion" in the composer but I understand your priorities. in reality I wanted to eliminate all the dialogs in...
Thx so much!! Zep Il giorno mer 24 ago 2022 alle ore 20:07 johnataylor < ***@***.***> ha scritto: > @ZepHakase22 we have a fix in the works > for this,...
My case is a little different. Let's say I have a root dialog that launches another dialog. The last dialog sent the client an Adaptive Card waiting for the client...