[FabianLars]

Rebase of #3986

Closes #4052

[netlify]

✅ Deploy Preview for tauri-v2 ready!

Name	Link
🔨 Latest commit	97ecbb2
🔍 Latest deploy log	https://app.netlify.com/projects/tauri-v2/deploys/6ad28b42a023b764a47b3e54
😎 Deploy Preview	https://deploy-preview-4042--tauri-v2.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 100 (no change from production) Accessibility: 98 (no change from production) Best Practices: 100 (no change from production) SEO: 100 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports
🤖 Make changes	Run an agent on this branch

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[netlify]

✅ Deploy Preview for tauri-releases canceled.

Name	Link
🔨 Latest commit	81add0a
🔍 Latest deploy log	https://app.netlify.com/projects/tauri-releases/deploys/6a74e509eaa18a0008509ce7

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	typedoc-plugin-frontmatter@​1.3.2
	starlight-typedoc@​0.23.1

View full report

[Legend-Master]

I wonder if it's possible to show the parameter types inline, instead of in a table below

compared to

[vasfvitor]

yeah afaik there's an option, btw should I bring it closer to v1 like the example section being up top?

[Legend-Master]

btw should I bring it closer to v1 like the example section being up top?

yeah if the parameter types are inlined with just the type references below, then they should be below everything else

[vasfvitor]

enum as table

expand objects


at reference/javascript/api/namespacedpi

---

https://deploy-preview-4042--tauri-v2.netlify.app/reference/javascript/api/namespacedpi/
without expand

with expand objects

[vasfvitor]

I'm going to rebase merge and do a bit of work on the css

[Legend-Master]

Also it seems like currently the functions were shown at the end, would it make sense to show them first? Since most of the useful things we provide are the functions as classes, the types, enums are all helpers

[vasfvitor]

you mean this?

specifically for this page https://deploy-preview-4042--tauri-v2.netlify.app/reference/javascript/api/namespaceapp/#type-aliases I'd argue that moving functions up would bury the other down below on the TOC. Unless the opposite is also true in other pages (many enum and helpers that hides the function on TOC), in that case either way this would be an issue so it ends as a matter of preference

[vasfvitor]

or I could reduce the toc depth to 2 levels

[Legend-Master]

Yeah that's what I meant. I wouldn't mind this too much either ways that this should only be for looking up certain APIs anyways

[vasfvitor]

@Legend-Master what do you think about the toc depth? It is also possible to remove the 'Functions', 'Enumerations' headings but I tried and it not so clear at glance

before/after toc depth (not same image but close)

before/after toc depth