when we register a class in the SearchView.row_meta dictionary, we now pass as a parameter a (global) function that is used to represent the object of the registered class.
this looks to me a bit of one biting one's own tail, I refer to the fact that this function should accept only one parameter and that it should be of the type of the class being described.
the name of the function could be more indicative of the fact that these functions are meant to provide text to be shown, on two separate lines, in the same row of a SearchView.
I propose removal of these functions and inclusion into the various classes, naming them something like search_view_markup_pair, not necessarily so but something like this, so the reader of the code has some idea of where the function will be used.
when we register a class in the
SearchView.row_metadictionary, we now pass as a parameter a (global) function that is used to represent the object of the registered class. this looks to me a bit of one biting one's own tail, I refer to the fact that this function should accept only one parameter and that it should be of the type of the class being described. the name of the function could be more indicative of the fact that these functions are meant to provide text to be shown, on two separate lines, in the same row of aSearchView. I propose removal of these functions and inclusion into the various classes, naming them something likesearch_view_markup_pair, not necessarily so but something like this, so the reader of the code has some idea of where the function will be used.