incubator-allura-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Van Steenburgh" <>
Subject [allura:tickets] #6190 Refactor custom fields
Date Tue, 18 Mar 2014 17:26:23 GMT
- **assigned_to**: Tim Van Steenburgh -->  nobody 


** [tickets:#6190] Refactor custom fields**

**Status:** open
**Milestone:** forge-backlog
**Labels:** cleanup 
**Created:** Wed May 01, 2013 07:58 PM UTC by Tim Van Steenburgh
**Last Updated:** Wed May 01, 2013 07:58 PM UTC
**Owner:** nobody


* It's depressing how many different places the code has to change if you were to add a new
type, for example
* `if` stmts around custom field types all over the place

The root problem I think is that custom fields are just dicts, so the logic ends up spread
all over the code instead of encapsulated in the object.


Sent from because is subscribed to

To unsubscribe from further messages, a project admin can change settings at
 Or, if this is a mailing list, you can unsubscribe from the mailing list.
  • Unnamed multipart/related (inline, None, 0 bytes)
View raw message