useResult deprecation question

[wreality]

Is it safe to assume that with getResult being removed from the documentation (rather than a deprecation note added to the documentation) that the intention is that it will be removed for the 4.0 release ?

Just figuring out where it needs to live in our project's priorities.

[Luferov]

And in general, why useResult is deprecated? What is the reason? Because this function is very usefull.

[Akryum]

@wreality Yes it will be removed before 4.0

@Luferov It's not that useful anymore now that optional chaining and nullish coalescing operators are available in standard JavaScript. So it makes sense to remove it to cleanup the API a bit.

[Luferov]

Yep, I agree, but if use one endpoint from library at project, what is good practice, use result is good solution for different queries. Because than I need always use result.data.foo, result.data.bar instead one solution useResult.

[Akryum]

You can write a function to do that:

export function autoPick (value) {
  const keys = Object.keys(value)
  if (keys.length === 1) {
    // Automatically take the only key in result data
    return value[keys[0]]
  } else {
    // Return entire result data
    return value
  }
}

And then use it like this:

const items = computed(() => autoPick(result.value))

Or write a composable version with the 'computed' part inside.

[Akryum]

I don't feel maintaining code and documentation for this is worthwhile in the library.

[Luferov]

Ok, thanks 🙏

[sschneider-ihre-pvs]

This might get a nightmare if you have https://eslint.vuejs.org/rules/no-side-effects-in-computed-properties.html on and try to swap out useResult for a computed.

[sschneider-ihre-pvs]

Well, yes, but it will also result in a lot of head scratching, since computed in this case might not be the right choice but maybe watch might help, just in reference to the deprecation text.

[Akryum]

Well, the third parameter of useResult was never supposed to contain side-effects in the first place.

[sschneider-ihre-pvs]

Well I would try and point at the documentation, but useResult is already gone :D

[sschneider-ihre-pvs]

Well, the third parameter of useResult was never supposed to contain side-effects in the first place.

What would be the correct place for side-effects?

[Akryum]

A watcher or onResult

[shtse8]

Any reason why undefined is trigger when loading? It is nightmare because all others using the result as a variable for their query will also be triggered when one is loading. How can I bypass the undefined value when using it as a variable of query but not for displaying?