BUG: Explorer Maximum results can't be set to less than 100

[Chaoscontrol]

Checks

• I have checked that this issue has not already been reported.

• I am using the latest version of Flow Launcher.

Problem Description

Title. When using a value higher than 100, the value is saved. When below 100, it gets adjusted to 100.

Video here

I'd like to set 5 in my case.

To Reproduce

1. Open Flow settings. Go to Plugins, expand Explorer settings.
2. Adjust Maximum results. Try setting 5. You'll notice it doesn't save. Try setting 105. It saves fine.

Screenshots

No response

Flow Launcher Version

1.19.5

Windows Build Number

10.0.26100.3476

Error Log

[deefrawley]

Can confirm it is regardless of index engine used

[Jack251970]

@jjw24 Any reason for this limit?

Flow.Launcher/Plugins/Flow.Launcher.Plugin.Explorer/ViewModels/SettingsViewModel.cs

Lines 527 to 528 in 9b28161

	public int MaxResultLowerLimit => 100;
	public int MaxResultUpperLimit => 100000;

[jjw24]

No technical reason for min value limitation, more how applicable it is to have less than 100 results. Max value limitation would be to do with performance impact.
#2874 (comment)

@Chaoscontrol what is the reason for setting it as 5? This means you have to be quite precise with your search query.

[Chaoscontrol]

@jjw24
Yes, I don't think 100 is a useful number tbh. Rarely anyone will like scrolling through a list of 100 results.

If there are so many results and the desired one is not in the first ones, the user will continue typing the query or adjust it. They won't scroll through 100 first.

In my case, I think a number like 5 or 10 would be enough.

[jjw24]

I also don't do much scrolling through the results, if I don't see the result in the first or second page I will likely redo my search query. Yeah I don't see any issues dropping down to min 5.

[Chaoscontrol]

I mean, for flexibility you might as well drop it to 1. I won't be using that low, but someone might want to use 3. Idk, unless there's any conflict, just allow the flexibility. If anything I would cap the upper value lower for performance reasons.