I see this kind of code too many times in a codebase. For example, it will be repeated for each variable inside jobData json object. This is an eyesore for the reader and makes it harder to understand the code.
Is there a way to set the root node in context.expand(...)? So, I could set the root node as jobData and refer to all the elements inside it without using the full path.
I guess I could also create a variable rootPath and keep changing it as needed. Would that work?
Re: Groovy best practices - How to set the root node when extracting data from a response?
Thanks. Is it okay to use JsonSlurper for a project at work? I wonder if this library is used widely in the software industry and specifically inside ReadyAPI. That would make me more confident about using it. I don't want a new library to become a hindrance because its hard to use, has no active maintainers etc.