Thim

hi @reinaldorossetti Not sure what is broken, since I was able to properly parse the XML example you shared. ```js const xml = 'xxx03.361.770/0001-58LibCPRD12341234MASSA ROBO1LibCundefined0102113601021FALSETRUETRUETRUETRUEQA TESTEQA TESTE'; const json =...

Hi @jekakos Not sure what you refer to, could you share an example? That way, we can better understand and assist.

hi @theold190 We will look into this, since it seems not the default behaviour. If possible could you share your the Portman config as well? That will allow us to...

hi @theold190 We were able to reproduce the issue. Behind the scenes Portman is using Postman library [openapi-to-postman](https://github.com/postmanlabs/openapi-to-postman) for doing the initial conversion. It seems like an issue in the...

hi @bpogrebi Can you share your Newman config? On the discussion board, there is an item on Newman CLI options, which might also be helpful: https://github.com/apideck-libraries/portman/discussions/289

hi @bpogrebi Thanks for the update, I'll have to give it a spin to figure out what is going wrong.

hi @bpogrebi, We found the cause and a PR is being reviewed. Cause: The Newman CLI expects options in param-cased format, while when using Newman as a NodeJS module the...

@bpogrebi The fix will be part of the next Portman release.

hi @bpogrebi , The issue was closed due to another tool. There is not a new release, I'm waiting for some input on another issue to release a new version...

hi @bpogrebi, We just released Portman v1.18.1, which includes the Newman fix.