WSO2 API Manager:对API进行分类和分组
从WSO2 AM 1.10迁移到2.0.不会提及我必须克服的所有障碍.但这很明显，令我震惊的是，在发布新版本之前，开发人员忽略/忽略了这一点.让我们忽略CSRF的所有错误，但是这也很麻烦:分组和分类.自上一个发行版以来，WSO2文档尚未更新，这有点令人遗憾.
Migrating from WSO2 AM 1.10 to 2.0. Won't mention all the obstacles I've had to overcame. But this one is pretty obvious and I am really stunned that this went overlooked/ignored by the developers before releasing the new version. Let's ignore all the bugs with CSRF, BUT this one sucks arse, too: Grouping and categorizing. WSO2 documents have not been updated since the last release, which is kinda sad.
-
BUG 1:除非"tags"目录下的所有子目录(在Carbon中)都小写，否则无论其原始名称/带有-group的标签如何，分组都不会起作用.
BUG 1: Grouping does not work unless all the subdirs (in Carbon) under "tags" dir are lowercased regardless of the original names / tags with -group suffices.
BUG 2:带有"-group"后缀的标签显示在左侧面板中(标签云").嗯.
BUG 2: The tags with "-group" suffix are displayed in the left panel (the "tag cloud"). Ehm.
BUG 3:在商店中显示的组标签是小写的，并且包含"-group"就足够了(上面两个bug的混合).
BUG 3: Group tags [displayed] at the Store are lowercased and contain "-group" suffices (mixture of both bugs from above).
BUG 4:组不支持空格(在标签云中).单击后，这些组将显示为空.
BUG 4: Groups do not support white spaces (in the tag cloud). When clicked, the groups appear empty.
有什么想法/解决方法吗?
Any ideas / workarounds?
如您所见，当您使用大写或空格定义API类别时，AM 2.0.0中存在一个错误.
As you observed,there's a bug in AM 2.0.0 when you defined the API categories with upper-case or with white spaces.
我创建了公共jira [1]来跟踪进度并在下一个即将发布的版本中进行修复.
I have created the public jira[1] to track the progress and fix by next coming release.
我检查了避免这些问题的可能性，发现可以通过子主题来避免在标签云中显示类别名称，而其他两个问题则使用大写&必须从代码级别固定空白.
I checked the possibilities of avoiding these issues and found that showing the category names in tag cloud can be avoid by a sub theme while other two issues with upper case & white spaces have to be fixed from code level.
要修复标签云中显示的类别，可以下载[1]中随附的template.jag并将其添加到子主题文件夹位置"AM/存储库/部署/服务器/jaggeryapps/store/site/themes/{ your_subtheme_name}/templates/tag/tag-cloud作为子主题模板文件，其内容如下[2].
To fix ,categories showing in tag cloud,you can download the template.jag attached in [1] and add it to sub theme folder location "AM/repository/deployment/server/jaggeryapps/store/site/themes/{your_subtheme_name}/templates/tag/tag-cloud" as a sub theme template file with following [2].