chore(Icons): make pathData async

[vladitasev]

UI5 Web Components Icons have a niche feature - exporting the SVG path string (pathData). This however causes issues as getTheme() must be called to determine which path version to export, and getTheme() is unreliable before boot() is complete. Now, we instead export a getPathData async function, that when awaited, will provide the said pathData.

This is how an icon accept.js is generated now:

import { isLegacyThemeFamilyAsync } from "@ui5/webcomponents-base/dist/config/Theme.js";
import { pathData as pathDatav4, ltr, accData } from "./v4/accept.js";
import { pathData as pathDatav5 } from "./v5/accept.js";

const getPathData = async() => {
	return await isLegacyThemeFamilyAsync() ? pathDatav4 : pathDatav5;
};

export default "accept";
export { getPathData, ltr, accData };

Technical note: onThemeRegistered used to call getTheme before boot was complete (and OpenUI5Support may change the outcome).

BREAKING CHANGE: UI5 Web Components Icons now export getPathData (function) instead of pathData (string)

If you used icons like this:

import "@ui5/webcomponents-icons/dist/accept.js";

or like this:

import accept from "@ui5/webcomponents-icons/dist/accept.js";

there is no change and no adaptations are required.

In the rare case you imported pathData from icons, for example:

import { pathData, ltr, accData } from "@ui5/webcomponents-icons/dist/accept.js";
console.log(pathData); // String containing the SVG path

you must change your code to, for example:

import { getPathData, ltr, accData } from "@ui5/webcomponents-icons/dist/accept.js";
getPathData().then(pathData => {
  console.log(pathData); // String containing the SVG path
});