Specify the priority between path_info and param #2
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hello Martin,
with the following patch I would like to give the user the opportunity to specify with mode_param{'priority'=>'param'} whether path_info or param should be the priority. At the moment if mode_param{'path_info' => 1} or similar is set, then always path_info is taken if it is not empty (this means is "/").
This patch gives the user more flexibility. You can specify a run mode with a hidden field or with a button and can display any path you want. Especially specifying a runmode with a button is at the moment not possible, when mode_param{'path_info'} is set to a true vale
There are no backward compatibility problems expectable because without the additional option, CGI::App behaves as always.
POD doc will follow the next weeks (perhaps earlier)
Best wishes,
Max