KhronosGroup / KhronosGroup/COLLADA2GLTF

Inconsistent ordering of GLTF JSON name property

Open
#226 3 comments 0 reactions 0 assignees View on GitHub
enhancement
Dominant language
C++
Stars
573
Forks
154
PR merge metrics
No merged PRs in 30d

Description

It seems that sometimes the `name` property is written first, and sometimes last.

That's because the base class `GLTF::Object::writeJSON` is not always called in the beginning of each override writeJSON method.

` GLTF::Object::writeJSON` also writes other properties like `extras` and `extensions`.

I think it is easier to debug and read the JSON when the `name` property always comes first?

Contributor guide

No contributing guide indexed for this repository

Research direction

Start at the GLTF::Object::writeJSON entry point and inspect each writeJSON override to compare where the base method is called. Ensure the name property is emitted consistently before the other properties written by the base class, including extras and extensions; verify the generated glTF JSON ordering.

Written by the indexing model from the issue text.

Assessment

Tech stack
cpp
Domain
tooling
Issue type
Refactor
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.