User tests: Successful: Unsuccessful:
Pull Request for Issue # .
This will pick up the category description and make it available to the output of the module.
No effect on backwards compatibility, as it doesn't change what exists now, merely adds one more attribute.
Use Case: When you're choosing to output subcategories, it might be useful in some cases to have more than just the category name available. Output templates that don't need it can ignore it safely, but this makes it available for the templates that might want to use it.
Will need to write a template override that includes the c_description field. Let me know if you want to borrow mine, either to use or as a reference while building your own.
Not sure if there's any. If you're documenting the fields available in a template override, then it would need to be added to that.
I've no idea from the test reports there whether the failure was in my code or in the travis setup code. If it's my code, point to where I can see what failed?
Status | New | ⇒ | Fixed in Code Base |
Closed_Date | 0000-00-00 00:00:00 | ⇒ | 2021-08-18 08:47:45 |
Closed_By | ⇒ | joomdonation |
OK on code review.