Tileset file extension (.tsx) conflicts with Typescript JSX files
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
This is a minor issue, but worth considering. Many systems already recognise .tsx files as TypeScript files that can be compiled to .jsx files. This means the system will open the .tsx files in a code editor by default instead of Tiled. Changing the default application is not a good solution for systems that have TypeScript and Tiled tileset files (such as mine).
I suggest changing the default file extension for tileset files. Maybe something like .tmsx?
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how Tiled identifies and opens tileset files, including the current .tsx extension and its file associations. Check whether changing the extension would affect existing tilesets or related documentation, then define the replacement extension and verify that tileset files still open correctly in Tiled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- desktop
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100