Skip to content
This repository was archived by the owner on Jan 27, 2022. It is now read-only.
This repository was archived by the owner on Jan 27, 2022. It is now read-only.

ELS producing an error regarding fail to compare number with nil? Read this. #81

@lze3

Description

@lze3

So, as a result of altercations regarding the versioning used with ELS, we had to change the version checking to ensure the functionality of it retained the same.

Old versioning would look similar to: 1.65, 1.93, 1.91, etc. This was easy to compare as those are all numbers. Despite its simplicity, it was quite impractical and creating updates and tags associated with a release was tedious. So, I implemented an automatic version bumper. This creates tags and releases for us whenever it determines a release to be worthy a release.

New versioning will look like:

Normal Versions

  • 1.0.3
  • 1.0.4

Beta Versions

  • 1.0.5b
  • 1.0.6b

Developer Versions

  • 1.0.7a
  • 1.0.8a

Of course, we don't want the normal person running a beta or development build in a production server, that could be detrimental. Warnings, logging and more will be specific to beta or development builds. You'll also receive a warning on resource start and version check if you are running a beta or development build.

If you encounter an error regarding comparing a number with nil, that's because you haven't updated.

There is no reason for you to be running older versions. If you encounter issues, report them, so we can fix them.

Thank you,
Zeemah.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions