This one is most likely going to turn out to be a research task, that in turn is going to produce some smaller, actionable tasks to actually remove the dependency on AUI here.
Goal: Port the Liferay.Ratings implementation from AUI — currently defined here:
- This module requires the "aui-ratings" module; we extend A.ThumbRating and A.StarRating. Will need to investigate exactly what the base YUI implementation provides.
- "git grep" results for "liferay-ratings" and "Liferay.Ratings": https://gist.github.com/wincent/af56fc14d99e6e032c17bdd0a6281a36
- There is a ratings taglib and it looks like we already ported the JS side to React: see https://github.com/liferay/liferay-portal/blob/master/portal-web/docroot/html/taglib/ui/ratings/page.jsp and https://github.com/liferay/liferay-portal/tree/master/modules/apps/ratings/ratings-taglib/src/main/resources/META-INF/resources/js/components/
So, I think the first step here is to analyze all this and figure out what we'll have to do to actually be able to migrate and/or deprecate the existing AUI based API. I haven't fully traced all the threads through, but given that the taglib already contains React component implementations, I am not sure how much of the AUI code is actually being exercised; if you look in the gist of "git grep" results you can see a handful of usages of the taglib, but nothing outside of the portal-web/docroot/html/taglib/ui/ratings/page.jsp actually referencing Liferay.Ratings itself — which is to say, that deprecating and pointing at the taglib might be an option.