Query Options mutator creates a hook instead of simple function

[matusgallik]

What are the steps to reproduce this issue?

1. use the following config:

override: {
				query: {
					shouldExportMutatorHooks: false,
					queryOptions: {
						path: './mutator.ts',
						name: 'customQueryOptions',
					},
}}

2. The generated helper functions to get query options follow the pattern use*QueryOptions.
3. remove the queryOptions from the config
4. the generated helper function is now called get*QueryOptions

What happens?

The function call to get the query options for a route become ahook.

What were you expecting to happen?

The name not to change comapred to the default settings

Any logs, error output, etc?

None

Any other comments?

This makes it rather difficult the use the option functions with eslint hook rules.

What versions are you using?

Operating System: Linux
Package Version: 6.25.0
Browser Version: N/A ?

[matusgallik]

@melloware is this an enhancement or a bug? Or differently; is this intended behavior? Thanks

[melloware]

I am not sure that is why I labeled it an enhancement because I wasn't sure if it was intended behavior or a bug...

[matusgallik]

@melloware any update on this?

[melloware]

No update.