Roundup Tracker - Issues

Issue 2551086

classification
Valid class names not documented. Should follow [A-z][A-z0-9_]+[A-z_]
Type: Severity: normal
Components: Documentation, Database, Test Versions: 2.0.0
process
Status: fixed fixed
:
: rouilj : rouilj, schlatterbeck, tekberg
Priority: normal : Effort-Medium

Created on 2020-07-27 03:55 by rouilj, last changed 2020-07-28 16:04 by rouilj.

Messages
msg6929 Author: [hidden] (rouilj) Date: 2020-07-27 03:55
Email thread:

  https://sourceforge.net/p/roundup/mailman/roundup-
users/thread/MWHPR08MB2941242ADD82F47F14E7FCAFCA7B0%40MWHPR08MB2941.namprd08.prod.outl
ook.com/#msg37065950

with subject "Trouble with new tracker designator?" on roundup users.

TL;DR

We need to restrict the format of classnames passed to the Class() method of the
hyperdb to --

  Alphabetic, one or more word char (alphabetic, numeric and _) and
  ending with an alphabetic or _

(Note classname can't easily end in a number as that makes it costly to
split the item number from the class name in a designator.)

Also modify splitDesignator() to match the classname format above and reject
all others.

Add tests for these cases.

Also need to find a place to document the class name restrictions. The design
doc only says has to start with an alphabetic.

This may drive a rewrite of the customizing doc to separate out API/internals 
documentation from actual customization examples. The current doc has grown
and it's tough to find things in there.

Do not allow leading _ at this time. We reserve it for future use if other
issues (e.g. the database tables names for user defined class names have
an _ prepended to the user class name) don't prevent it from being used.
msg6930 Author: [hidden] (rouilj) Date: 2020-07-28 16:04
fixed in rev6238:6834bb5473da till rev6243:1e53e3ad9e5c
(yeah....)
History
Date User Action Args
2020-07-28 16:04:41rouiljsetstatus: new -> fixed
resolution: fixed
messages: + msg6930
2020-07-27 03:55:52rouiljcreate