Tamara

You really don't need to bump your messages. You'll just need to be a bit patient, sometimes it takes a while in order to get a reponse 🙂

Tamara

Hi all, I've got a jquery conflict with the userforms module. I figured I'd ask in here before creating an issue in the repository. On the userform page there are 2 jquery files loaded: 1 is loaded through my own (custom) Page_Controller, the other through the UserDefinedForm_Controller. In the console error I see some conflict issues. How can I fix this? I really need to keep my own jquery file, so removing that isn't an option for me.

Tamara

I'm not sure. Try looking it up through Google 😉

Tamara

Another question... is it possible to set certain fields which are set through the TypeCreator as optional? (if so, how?)

Tamara

Is GraphQl somewhat backwards compatible? E.g. with different API versions?

bummzack

Graphql is much better than rest in that regard. I‘m not an expert, but AFAIK you can deprecate individual fields, map them to other fields etc. No need for new endpoints

bummzack

Maybe this gives some insight into the possibilities: https://www.apollographql.com/docs/graphql-tools/schema-directives.html

Show 1 attachment(s)
Schema directives | GraphQL Tools

Using and implementing custom directives to transform schema types, fields, and arguments

Hide attachment content
chillu

You can “convert” a REST API into a (simple) GraphQL API by routing GraphQL requests through to traditional REST

flamerohr

The main problem I've seen with backwards compatibility in graphql isn't really related to graphql directly - and that's when a field changes type, but it's more to do with the consumer's assumptions