This is the kicker for making this module much more useful. How to create a Views field for each attribute?
Can multiple handlers be added in the same handler file? If so, it could be possible to loop through the attributes array in uc_views_attribute.views.inc to create the view handler names, then loop through the attributes array in uc_views_attribute_handler_WHATEVER.inc to create the actual handlers. If all the handlers can be the same format (text, numeric, etc.) this could work.
There are two big ifs to look into above.
This is the kicker for making this module much more useful. How to create a Views field for each attribute?
Can multiple handlers be added in the same handler file? **If so**, it could be possible to loop through the attributes array in `uc_views_attribute.views.inc` to create the view handler names, then loop through the attributes array in `uc_views_attribute_handler_WHATEVER.inc` to create the actual handlers. **If** all the handlers can be the same format (text, numeric, etc.) this could work.
There are two big **if**s to look into above.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
This is the kicker for making this module much more useful. How to create a Views field for each attribute?
Can multiple handlers be added in the same handler file? If so, it could be possible to loop through the attributes array in
uc_views_attribute.views.incto create the view handler names, then loop through the attributes array inuc_views_attribute_handler_WHATEVER.incto create the actual handlers. If all the handlers can be the same format (text, numeric, etc.) this could work.There are two big ifs to look into above.
Maybe if the data were deserialized in
uc_views_attribute.views.incthey could use a generic handler?