Content types is fetched differently depending on imageSelector and ImageSelector xml

poi33 commented 4 years ago

While using lib-guillotine we noticed that this xml:

<input type="ImageSelector" name="image">
        <label>Cover</label>
        <config>
        </config>
</input>

Does not return the same data as

    <input type="imageSelector" name="image">
            <label>Cover</label>
            <config>
            </config>
        </input>

While the bottom is a small typo it did return the id string. `image: "59e6aa08-5fce-4dec-8386-7090eaa48ab2" The top one resolves to and image and returned a structured image graph.

image: {
    _id: "59e6aa08-5fce-4dec-8386-7090eaa48ab2"
    [...]
}

sigdestad commented 4 years ago

It is a question If the type value should be case sensitive or not. I believe it should not (like oretty much everything else i XP.

How is the general CTY implementation handling this?

rymsha commented 4 years ago

CTY? Center for Talented Youth?

anatol-sialitski commented 4 years ago

Dynamic types are case-sensitive on Guillotine. For now please use ImageSelector instead of imageSelector. Otherwise you should be able to see in logs the message likes that Unknown input type [' + input.inputType + ']. Using String as GraphQL type

enonic / lib-guillotine

Content types is fetched differently depending on imageSelector and ImageSelector xml #64