Why block syntax needed for options?

[ziy]

Why do we need to put a vertical bar to make the options as a block? For example,

pipeline:
  - inherit: ecd.phase
    name: keyterm-expansion
    options: |
      - inherit: helloqa.keyterm.simple

It might be more intuitive to have the value type for the key "options" as a list (aka an Iterable), so that parameter value can be flattened to higher layers, and we will be one step closer to present the "effective yaml description".

pipeline:
  - inherit: ecd.phase
    name: keyterm-expansion
    options:
      - inherit: helloqa.keyterm.simple
        param: value

[elmer-garduno]

Yes I agree with the intuition, but I guess it's done in that way to make
it consistent with the inherited parameters? As they are parsed as strings.

Does that makes sense?

On Tue, Apr 2, 2013 at 10:09 PM, Zi Yang [email protected] wrote:

Why do we need to put a vertical bar to make the options as a block? For
example,

pipeline:

• inherit: ecd.phase
  name: keyterm-expansion
  options: |
  • inherit: helloqa.keyterm.simple

It might be more intuitive to have the value type for the key "options" as
a list (aka an Iterable), so that parameter value can be flattened to
higher layers, and we will be one step closer to present the "effective
yaml description".

pipeline:

• inherit: ecd.phase
  name: keyterm-expansion
  options:
  • inherit: helloqa.keyterm.simple
    param: value

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17
.

[elmer-garduno]

I also remember having problems parsing nested things inside the inherits
that's why the ! syntax was there. But maybe that's old stuff and we can
move on.

On Tue, Apr 2, 2013 at 10:27 PM, Elmer Garduno [email protected] wrote:

Yes I agree with the intuition, but I guess it's done in that way to make
it consistent with the inherited parameters? As they are parsed as strings.

Does that makes sense?

On Tue, Apr 2, 2013 at 10:09 PM, Zi Yang [email protected] wrote:

Why do we need to put a vertical bar to make the options as a block? For
example,

pipeline:

• inherit: ecd.phase
  name: keyterm-expansion
  options: |
  • inherit: helloqa.keyterm.simple

It might be more intuitive to have the value type for the key "options"
as a list (aka an Iterable), so that parameter value can be flattened to
higher layers, and we will be one step closer to present the "effective
yaml description".

pipeline:

• inherit: ecd.phase
  name: keyterm-expansion
  options:
  • inherit: helloqa.keyterm.simple
    param: value

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17
.

[ziy]

But for things outside the "options", we can achieve this without the block syntax and we can also put paramters. For example,

collection-reader:
  inherit: helloqa.collection.collection-reader

[elmer-garduno]

You are right it might be time to try again without blocks

On Tue, Apr 2, 2013 at 10:35 PM, Zi Yang [email protected] wrote:

But for things outside the "options", we can achieve this without the
block syntax and we can also put paramters. For example,

collection-reader:
inherit: helloqa.collection.collection-reader

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/17#issuecomment-15814540
.