feat(native): add native settings section

[marekvospel]

This pull request adds a settings section that is only shown in elk native app and minimize_to_tray configuration option.

Related

elk-zone/elk-native#58

[stackblitz]

Run & review this pull request in StackBlitz Codeflow.

[netlify]

✅ Deploy Preview for elk-docs canceled.

Name	Link
🔨 Latest commit	1c1dad0
🔍 Latest deploy log	https://app.netlify.com/sites/elk-docs/deploys/6453e91d3b8d1200088c2d93

[netlify]

✅ Deploy Preview for elk-zone ready!

Name	Link
🔨 Latest commit	1c1dad0
🔍 Latest deploy log	https://app.netlify.com/sites/elk-zone/deploys/6453e91d93c261000819174c
😎 Deploy Preview	https://deploy-preview-1414--elk-zone.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site settings.

[patak-dev]

I wonder if we should add these options in elk-native itself, we should be able to add some hooks to extend the options 🤔
cc @danielroe @JonasKruckenberg

[danielroe]

Yes. We could potentially also move the tauri module that exists in this repo -> elk native repo itself.

[JonasKruckenberg]

I don't know how we would integrate this with the current submodule setup, but if you have any smart ideas, moving as much elk-native specific code into that repo sounds like a good solution to me generally

[marekvospel]

I don't think it would be possible to move the tauri module into elk-native repository, as that could cause some type issues (just adding tauri-runtime-only types in this repository I had problems with types, see https://github.com/elk-zone/elk/blob/8bd02816203f5e00c7440689a877a5888107613a/modules/tauri/runtime/native-settings-undefined.ts)

At least I can't think of any good and easy solution

[marekvospel]

I've resolved the merge conflicts. Should we wait till elk-zone/elk-native#65 is resolved before merging this?

I feel like for now we could just merge it and once it is decided whether we will continue to use git submodules or start using other methods, just migrate some of this code. I'll gladly migrate this into elk-native once and in case it is necessary.

[marekvospel]

@JonasKruckenberg This method could be added to tauri-plugin-store to make it easier to work with the values reactively. However it is framework specific, so there could be some problems with dependencies and other framework integrations would probably need to be added.

elk/modules/tauri/runtime/native-settings.ts

Lines 8 to 35 in c383d93

	async function tauriStoreRef<T>(store: Store, key: string, defaultValue: T): Promise<TauriStoreRef<T>> {
	let refValue = defaultValue
	const ref = customRef<T>((track, trigger) => {
	store.onKeyChange(key, (value) => {
	refValue = value as T
	trigger()
	}).then()
	return {
	get: () => {
	track()
	return refValue
	},
	set: async (value: T) => {
	await store.set(key, value)
	await store.save()
	refValue = value
	trigger()
	},
	}
	})
	const result = await store.get(key)
	if (result !== undefined && result !== null)
	refValue = result as T
	return ref
	}

[marekvospel]

@Shinigami92 any chance for a review? This PR has been sitting here without any activity for a while

[Shinigami92]

I could just do a code review
I don't use the native tauri app, you should ask someone else that is more familiar with the tauri app

[marekvospel]

I could just do a code review I don't use the native tauri app, you should ask someone else that is more familiar with the tauri app

@JonasKruckenberg could you please take a look at this when you're free?

[Shinigami92]

Could you please explain why it is needed to have this -undefined version?
Cant this be e.g. inlined like addImports({ name: 'useNativeSettings', from: () => undefined }) or similar?

[marekvospel]

The reason I added the -undefined version is, that the non-undefined version cannot be imported unless in tauri environment.

It also serves the purpose of setting the types for the function (NativeSettings | undefined), because they wouldn't be generated in the prepare command, as the module returned before defining the global import.

I had no idea it was possible to import it inline, I'll take a look into it.

[marekvospel]

I didn't find any way to add an import inline, the import object requires from: string value, and I couldn't find any other auto import releated function, that would do such a thing.