Initially it was to make the I go to "<url>" Step to go to an arbitrary url. It morphed into just expanding some behavior to allow PleadingPower to pass tests. Probably stuff we needed anyway, but probably not stuff that should be in a PR all together. The new Step isn't really necessary any more for this particular purpose, but I've been meaning to add it.
All changes should be listed in the changelog.
Links to any solved or related issues
N/A
Any manual testing I have done to ensure my PR is working
The only way I was able to test the more robust addition to the trigger variable name flow was with PleadingPower. We don't have a server that has the necessary restriction (config restrict input variables=True), so we don't have a way to test handling that restriction.
plocket
commented
6 months ago
In this PR, I have:
Reason for this PR
Initially it was to make the
I go to "<url>"Step to go to an arbitrary url. It morphed into just expanding some behavior to allow PleadingPower to pass tests. Probably stuff we needed anyway, but probably not stuff that should be in a PR all together. The new Step isn't really necessary any more for this particular purpose, but I've been meaning to add it.All changes should be listed in the changelog.
Links to any solved or related issues
N/A
Any manual testing I have done to ensure my PR is working
The only way I was able to test the more robust addition to the trigger variable name flow was with PleadingPower. We don't have a server that has the necessary restriction (config
restrict input variables=True), so we don't have a way to test handling that restriction.