Open gschulze opened 3 months ago
Yea this is a bit of a wart that has developed over the years. I'll leave this issue open to remind us when we set up for 2.0
@SeppahBaws what to do think about getting this done along with the upcoming 2.0
release?
Yep sounds good. Are you talking about houdini-svelte
2.0 or houdini
2.0 here?
Maybe it's also worth creating a milestone or two here in github so we have a more clear view of what we want to add/fix when?
Are you talking about houdini-svelte 2.0 or houdini 2.0 here?
Whichever needs the change. We're going to have to roll out 2.0 versions for both since the graphql version will change
Maybe it's also worth creating a milestone
Good idea! I went ahead and did that.
Describe the feature
I discovered that there are two types that are quite similar:
Result
andQueryResult
.One is defined as:
the other one as
Why is it called
isFetching
one time andfetching
the other? I'm asking because our project uses derived stores, which propagate thefetching
field with a transformeddata
field. Instead of defining our ownResult
type, I would rather use an existing one, so I discovered the inconsistency.It would be nice if these types used the same name for all fields.
Criticality
None