HTTP action output map does not create new fields on pubs

[gabestein]

An obscure one, and unclear exactly what the expected behavior should be, but just to have it logged...

What went wrong, step-by-step?

1. Create a pub
2. Run an HTTP action that maps a response to a field that does not exist on the pub type (and that was not added to the pub via a form)
3. HTTP action will report successfully mapping the output, but will not create a new field)

What did you expect to happen?

HTTP action creates a new field with the mapped output value on the pub

What URL can we use to see the issue?

What browser/operating system were you using?

Optional

Have any screenshots? (Attach them by dragging the image here)

Who reported this? (If not you)

[tefkah]

Should this be: "creates a new value on the pub for the specified field"?
I don't think it should be creating a new field entirely right?

[gabestein]

Yeah, I'm not exactly clear what the behavior should be, so pretty low priority here.

But if you, for example, add a field to a pub type, but there are old pubs created before that fields was added, it won't add the value. Maybe what we should actually do is add fields to existing pubs of that type when we do that? Either way, just wanted to have it documented.