Should a classification be added to distinguish between tauri1 and tauri2?

[RSS1102]

This way, users can better learn from different versions of tuari's code. Of course, adding an action to automatically update would be the best. Prevent users from updating the version of Tauri. Either open source or closed source can be updated through actions.

[vasfvitor]

forget it, I was tripping
at any moment have you been confused whether the docs is referring to Tauri v1 or v2? Because the current docs it's v2 only.

v1 docs is at https://v1.tauri.app/

[RSS1102]

I'm referring to the repo or project of README.md, indicating whether it was built with tauri1 or tauri2

[vasfvitor]

sorry I'm at the wrong repo lol, you're right, it should be distinguished

[vasfvitor]

got lost here with them urls

[RSS1102]

@vasfvitor @FabianLars hi ~
So have any ideas? Or plans? Or anything I can try to do? or I can try it first？

[FabianLars]

idea would be to just go with simple badges like for Closed Source - probably for both v1 and v2 so each entry has a badge.

i think 2 seperate lists would be annoying when apps update but i wouldn't mind it too much if we basically move the current list into a collapsed section and only merge PRs for v2 stuff

i have no time to work on this myself

[RSS1102]

OK, I will try to write a script to add v1/v2 badges. Closed-source resources can only wait for the author to submit the version (but there is no code reference value for others)

Yes, v1 is not necessary in a new project after all. After all, new projects should create tauri@v2 to get support.