Resolve object types and properties should be split into two?
Open
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 12.9k
- Forks
- 2k
- Avg merge
- 4h 27m
- Merged PRs (30d)
- 8
Description
{
"gid":3993,
"height":32,
"id":310,
"name":"shutter2",
"rotation":0,
"type":"foo", // i just need the type written out and not all the props
"visible":true,
"width":32,
"x":1536,
"y":1248
},
These should be really split into two parts:
- Resolve object types
- Resolve object properties
because I only need object types resolved and not the properties themselves as I prefer to save safe and do a lookup.
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
No file or test is named in the issue. Start by locating the Tiled code that resolves the object JSON shown in the report, then trace how its type and properties are handled. Done means object types can be resolved independently of object properties so callers can perform a later lookup.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- game-dev, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100