Disabling / controlling path parameter imputation?

[tfmorris]

I have an API that I'm trying to analyze using the desktop app on Mac which has a structure like

/command/core/get-preference?param=

where core is the module name and the command is get-preference.

Unfortunately, demystify seems to have decided that the command structure is /command/{command}/{param3} and has mushed all the query parameters together when they really varying by command.

The desktop app doesn't seem to have any preferences or other controls that I can find. Is there any way to disable this behavior?

[AndrewWalsh]

Hi @tfmorris ,

Imputation uses the following heuristic, but some faults have become apparent. In particular, paths with the same length "/a/b, /a/c, ..." are considered the same when they have the same response, but this falls over as many APIs do not serve a response and this is therefore being incorrectly determined as equivalent. This is the same data rule in the link.

Have you tried OpenAPI DevTools? Imputation is manual on that.

I had planned to either resolve this or add new options, but I don't intend to continue this project.

Thanks,

Andrew

[tfmorris]

Thanks for the reply. That's too bad that you aren't continuing the project. It seems pretty useful. I actually started at OpenAPI DevTools, but its Readme says that it's ended as well, pointing here.

I actually independently found and removed the automaticParameterisation function, confirming that it was the source of the problem. After learning about Wails (called wails3 by the build), Task, and probably other stuff I'm forgetting, as well as updating my Go, NPM, etc, I was able to bumble my way through building a new desktop app and confirmed that the patched version worked for my use case. I went with the desktop app because I wanted to drive things with my Cypress test suite and wasn't sure how that would interact with the browser plugin.

Thanks for the useful tool and the quick response.

[AndrewWalsh]

@tfmorris that's good to hear. Automatic parameterisation can be disabled without issue, and could be fixed by updating the heuristic. I may get round to a fix some day, but for now I'll just leave this open.