You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, Meta v3 adopts both kebab-case (ex: the v3/versions/quilt-mappings route) and camelCase (ex: the gameVersion field on all mappings objects); Considering that the project in general is pushing for snake case as a standard case, the meta should also follow these steps and adopt it too; Applying this change should be simple, considering that the above examples of casing are likely to be the only ones on the meta itself
The exceptions for this is of course, the launcher profile metadata, which isn't really meta-y but rather "hey installers! we're giving you a file for free", with those files being meant to be read by Minecraft launchers in the end, who expect camelCase
For an example of it being used for API, see Modrinth's meta
The text was updated successfully, but these errors were encountered:
Currently, Meta v3 adopts both kebab-case (ex: the
v3/versions/quilt-mappings
route) and camelCase (ex: thegameVersion
field on all mappings objects); Considering that the project in general is pushing for snake case as a standard case, the meta should also follow these steps and adopt it too; Applying this change should be simple, considering that the above examples of casing are likely to be the only ones on the meta itselfThe exceptions for this is of course, the launcher profile metadata, which isn't really meta-y but rather "hey installers! we're giving you a file for free", with those files being meant to be read by Minecraft launchers in the end, who expect camelCase
For an example of it being used for API, see Modrinth's meta
The text was updated successfully, but these errors were encountered: