> Technically that sortField should allow sorting by tiddler titles > ascending or descending but it doesn't seem to be used. > > I can't seem to be find any reason for it in the history. > Personally I'd remove it since title is the only thing that can be > sorted and currently they are returned in alphabetical order. Doing > a .reverse() will get the opposite order.
Some core functions were initially created as wrappers to provide useful entry points for plugins to do what they need. While the core code isn't currently using the 'sortfield' parameter, it can still be used by plugins that have implemented their own alternative handling for getting and sorting the missing tiddlers list. Even though getMissingTiddlers() only returns tiddler *titles* (not tiddler *objects*), those titles can still be sorted by other criteria *before* being returned. Once returned, sorting by other than the title text can become costly, requiring lookups of each tiddler to get the associated data values to sort by. For this particular function, the impact of changing the existing API is probably minimal.. however, the principle is very important: removing existing parameters from TWCore functions should NOT be done for mere "cleanup" reasons. There should always be *compelling* technical reasons for API changes, and just because the TWCore isn't using a parameter, doesn't mean that it isn't there for a reason. -e -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/tiddlywikidev?hl=en.
