Brief summary of issue / Description of requested feature:
For development of a new package repository we need to enforce these fields as they are important for showing information to the end user describing a package.
The version field should only be a valid number to make package version comparisons simple and should follow basic semantic versioning rules, but without a patch level. ie. 2 and 2.1 is valid, 2.1.1 is invalid. Letters should not be allowed. We can use third party library for comparisons as mentioned below.
Steps to reproduce the issue / Reasons for adding feature:
To aid in development of a simplified, centralised package repository.
Error output / Expected result of feature
Exported mpackage file will contain full information in config.lua
Extra information, such as the Mudlet version, operating system and ideas for how to solve / implement:
Previous discussions: #3067, #3069, #2289
https://discord.com/channels/283581582550237184/283582439002210305/1248621987140735140
Brief summary of issue / Description of requested feature:
For development of a new package repository we need to enforce these fields as they are important for showing information to the end user describing a package.
The version field should only be a valid number to make package version comparisons simple and should follow basic semantic versioning rules, but without a patch level. ie. 2 and 2.1 is valid, 2.1.1 is invalid. Letters should not be allowed.We can use third party library for comparisons as mentioned below.Steps to reproduce the issue / Reasons for adding feature:
To aid in development of a simplified, centralised package repository.
Error output / Expected result of feature
Exported mpackage file will contain full information in config.lua
Extra information, such as the Mudlet version, operating system and ideas for how to solve / implement:
Previous discussions: #3067, #3069, #2289
https://discord.com/channels/283581582550237184/283582439002210305/1248621987140735140