#3926 Project macro - improved filtering
We currently support filtering on labels, awards, and categories. Categories are old and not used any more - instead, we use "trove". We should remove category filtering and add filtering for trove. It just needs to work for simple filtering, no complex "and"/"or" logic like labels have. Trove values can be set in the project admin page for categorization. Filtering by id # is good enough (as opposed to trove name)
Originally by: *anonymous
The corresponding 42cc ticket - #11: [3926] Project list filtering
Originally by: *anonymous
What do you think is better to pass with trove argument - full name(OSI-Approved Open Source) or fullpath(License :: OSI-Approved Open Source)?
Those will be cumbersome to pass as arguments to the macro. Let's use shortname (osi).
Originally by: jeyivanov
Sorry for anonymous message above.
Originally by: jeyivanov
It's cumbersome but very obvious - user can just copy/paste the full path and that's all. And user should know shortname for every trove - won't it be a problem?
I was thinking that it might be hard to make the macro parsing work with spaces and quotes, like
[[projects category="License :: OSI-Approved Open Source"]]. But maybe that will work just fine. And you are right about having to know the short name.Originally by: jeyivanov
Parsing is ok.
And as I can see there is now need to replace the argument itself - [[projects trove=""]] instead of [[projects category=""]].
"trove" is used mostly internally so I'd prefer not to show that to people. Since we are removing the "category" logic we can re-use that name.
Fixed #11 and pushed changes to 42cc_3926