🚀 Feature Request
Current Problem
Currently, the library has not been officially released. Therefore, only SNAPSHOT builds are used in applications like the webinterface. This makes it hard to trace back errors if the used library version is unclear.
Proposed Solution
Add a new functionality, like a getLibraryVersion() method, that returns the current version of the library. Since there is (currently) no versioning scheme like semantic versioning, the method should return an identifier that helps to trace back the correct version. This could be a hash based on the last commit (usage of git rev-parse) or current source code or something similar.
Additional Context
This might only be an interim solution until an official release with semantic versioning.
🚀 Feature Request
Current Problem
Currently, the library has not been officially released. Therefore, only SNAPSHOT builds are used in applications like the webinterface. This makes it hard to trace back errors if the used library version is unclear.
Proposed Solution
Add a new functionality, like a
getLibraryVersion()method, that returns the current version of the library. Since there is (currently) no versioning scheme like semantic versioning, the method should return an identifier that helps to trace back the correct version. This could be a hash based on the last commit (usage ofgit rev-parse) or current source code or something similar.Additional Context
This might only be an interim solution until an official release with semantic versioning.