You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 5, 2020. It is now read-only.
liferay-theme-tasks 10.0.0-alpha.1+gulp 4.0.0 on Windows - Generated theme is deployed as a portlet instead of a theme, and it cannot be applied to site.
#458
Closed
zhangyan0701 opened this issue
Apr 1, 2020
· 1 comment
We will use liferay-npm-build-tools-common to handle path with the FilePath
class.
Note that we already have liferay-npm-build-tools-common as a dependency in the
generator, and that this package will be used to contain common JS Toolkit code
in the near future.
izaera
pushed a commit
to izaera/liferay-js-themes-toolkit
that referenced
this issue
Apr 6, 2020
Instead of using a plain object, we will make a class with structure to hold
options.
This is to be able to track changes to the options schema, type each value, and
detect incorrect usages (thus the Object.freeze, to avoid spurious storage of
options).
izaera
pushed a commit
to izaera/liferay-js-themes-toolkit
that referenced
this issue
Apr 6, 2020
Steps to reproduce:
Expected Result:
The generated theme should be listed in Themes tab.
Actual Result:
The generated theme is listed in Portlets tab.
The text was updated successfully, but these errors were encountered: