Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Support kotlin.collections.Set
See original GitHub issueIs your feature request related to a problem? Please describe.
Right now the current support collections we can convert to a GraphQL list (List, Array) to do provide a uniqueness guarantee like Set
Describe the solution you’d like
We would like to use a Set<T> as a unique collection of values instead of a List<T> or Array<T>
Describe alternatives you’ve considered
We could use List in the schema code but then we would have to manually perform some operation to remove duplicates in the list
Additional context
This is the error that is thrown when Set is used in the schema
Cannot convert kotlin.collections.Set<kotlin.String> since it is outside the supported packages [com.expedia]
Issue Analytics
- State:
- Created 4 years ago
- Comments:6 (5 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
@tapaderster The team brought up a good point that while
Sets could be used from a server perspective that information is not part of the GraphQL spec so clients could pass in a list of items as input but if the server used aSetas the input then it would remove those items. The developer may want to do this but I feel like this would be an implementation detail and shouldn’t be part of the schema serialization/deserialization.My point being GraphQL really only supports lists, so we should as well. Does everyone agree?
See updated discussion: https://github.com/ExpediaGroup/graphql-kotlin/discussions/1110
You can add
Setsupport with custom hooks