Skip to content

Sanitise the version number on release notes #16

@johnmunster

Description

@johnmunster

What problem does this address?

In its current state the version number field allows any characters to be input - http://bigbite.im/i/8pjF2S

What is your proposed solution?

Given that the version number should follow semantic versioning (MAJOR.MINOR.PATCH) numbering, I am suggesting the following features be implemented to:

  1. Sanitise the field so it only accepts numbers.
  2. Only allow the release note to be published once it the version number is input and in the correct format.
  3. (optional) Have it so the version number increments on the previous number.
  4. (optional) UI/UX change to the field so that it is 3 fields for each number instead of 1 field - http://bigbite.im/i/gNDeta (crude mock up)

Metadata

Metadata

Assignees

Labels

enhancementNew feature or request

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions