Ticket #483 (closed enhancement: fixed)

Opened 18 months ago

Last modified 4 months ago

Property metadata annotations

Reported by: kasper Owned by:
Priority: high Milestone: AnalyzerBeans 0.10
Component: AnalyzerBeans Keywords:
Cc:
Influenced classes:

Description

Unfortunately the type of a @Configured property is not always enough to say exactly how the expected behaviour of the property is. We need to be able to attach more metadata about each individual property. Examples could be:

  • For numbers: Min, Max number
  • For strings: Single line or multi line
  • For files: Is it an existing file (to be opened) or a new file (to be written)
  • for arrays: Is there a min- and max-size

Attachments

patch.txt Download (5.7 KB) - added by paritoshranjan 17 months ago.
Patch for StringProperty? annotation

Change History

comment:1 Changed 18 months ago by kasper

Another one:

  • For all properties: Order of property when presented to user (ie. A is no. 1, B is no. 2)

Changed 17 months ago by paritoshranjan

Patch for StringProperty? annotation

comment:2 Changed 17 months ago by kasper

  • Status changed from new to closed
  • Resolution set to fixed

Thank you, the patch is approoved and you've been granted commit access.

comment:3 Changed 17 months ago by kasper

  • Status changed from closed to reopened
  • Resolution fixed deleted

Oops didn't mean to set the whole ticket as complete :)

comment:4 Changed 16 months ago by kasper

  • Milestone changed from AnalyzerBeans-0.1 to AnalyzerBeans-0.2

comment:5 Changed 4 months ago by kasper

  • Status changed from reopened to closed
  • Resolution set to fixed

Marking this as closed for now, since attention to this concept has been there for a long time and will continue to be whenever a new metadata need occurs. As such the issue is more a general concern of AnalyzerBeans than a specific task to implement now.

comment:6 Changed 4 months ago by kasper

  • Milestone changed from AnalyzerBeans X.0 to AnalyzerBeans 0.10

Releasing with AnalyzerBeans 0.10.

Note: See TracTickets for help on using tickets.