KETTLE-56: Allow the definition of a Kettle requestHandler to accept "options" in addition to type/gradeNames

Metadata

Source
KETTLE-56
Type
Improvement
Priority
Major
Status
Pull Request
Resolution
N/A
Assignee
Antranig Basman
Reporter
Antranig Basman
Created
2017-01-09T21:18:53.334-0500
Updated
2020-11-04T18:20:36.428-0500
Versions
N/A
Fixed Versions
N/A
Component
N/A

Description

By analogy with other locations, e.g. the IoC testing framework's "sequence grades", we should permit free-form "options" to appear in the definition of a requestHandler - this promotes reusability in cases where parameterisation is light, allowing the entire definition to be written out inline in the handler definition.

Comments

  • Antranig Basman commented 2017-01-09T21:23:29.210-0500

    Well, anticipating the FLUID-5750 "options flattening revolution", we should simply accept "whatever other" options are in its definition as component options - and this is only consistent with our existing acceptance of top-level "gradeNames".

  • Antranig Basman commented 2020-06-12T14:40:30.350-0400

    This is in progress in the KETTLE-78 pull: https://github.com/fluid-project/kettle/pull/52