You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@allura.apache.org by Tim Van Steenburgh <va...@users.sf.net> on 2014/03/18 18:26:23 UTC

[allura:tickets] #6190 Refactor custom fields

- **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

Symptoms:

* 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 sourceforge.net because allura-dev@incubator.apache.org is subscribed to https://sourceforge.net/p/allura/tickets/

To unsubscribe from further messages, a project admin can change settings at https://sourceforge.net/p/allura/admin/tickets/options.  Or, if this is a mailing list, you can unsubscribe from the mailing list.