Feature request: never fail when calling removeFields (guillotine 7)

Features
1

It would be nice if the params.removeFields() didn’t fail if the fields don’t exist.

2

Hi Amund,

I can not reproduce it. The removeFields function works fine.

3

@Amund0 do you have an example we could use to reproduce the problem, or did you figure it out?

4

Hi Amund,

We released Guillotine 7.1.

Now developers can change the behavior of what should happen when calling modifyFields function with unknown fields. By default, it will throw an error, helping developers to identify when they have done something wrong.

To prevent an error, developers can use the graphql.extensions.modifyUnknownField=warn configuration in the com.enonic.app.guillotine.cfg file. More information about the configuration settings can be found here.

1 Like