Position callsign format bug

[jvoss]

In gitlab by @jvoss on Nov 1, 2017, 21:38

Fix position callsign format validation to allow two letter callsigns: eg. XX_XX_CTR

Currently checks for 3 letters (XXX_XXX_XXX)

[jvoss]

In gitlab by @jvoss on Nov 3, 2017, 16:46

The regular expression used to validate a position callsign is currently: /^[A-Z]{3}([A-Z0-9]{1,3})?[(FSS|CTR|APP|DEP|TWR|GND|DEL)]{3}$/

This does not match a position such as: KC_CTR

Need to do more research to see if there are any other variations that it would not match. Otherwise simply changing to the following should work: /^[A-Z]{2,3}([A-Z0-9]{1,3})?[(FSS|CTR|APP|DEP|TWR|GND|DEL)]{3}$/

[jvoss]

In gitlab by @jvoss on Nov 9, 2017, 15:24

Also need to be able to support callsigns beginning with 4-letters: EIDW_APP

[jvoss]

In gitlab by @jvoss on Nov 11, 2017, 15:22

created branch 16-position-callsign-format-bug

[jvoss]

In gitlab by @jvoss on Nov 11, 2017, 15:48

mentioned in commit f109d3cc4aeb761d8b9ba3a7a92a666c0d82ce54

[jvoss]

In gitlab by @jvoss on Nov 11, 2017, 15:49

mentioned in merge request !19

[jvoss]

In gitlab by @jvoss on Nov 11, 2017, 15:51

closed via merge request !19

[jvoss]

In gitlab by @jvoss on Nov 11, 2017, 15:51

closed via commit 67b47a2790b2230f0fb47c9363b23e3a3c1a5c3e

[jvoss]

In gitlab by @jvoss on Nov 11, 2017, 15:51

closed via commit f109d3cc4aeb761d8b9ba3a7a92a666c0d82ce54