Replies: 2 comments
-
|
I did some testing on this, and there is more work required. With reference to the manifest example below:
Manifest example: modules:
jira:globalPage:
- key: ui-kit-2-test-hello-world-global-page
resource: main
resolver:
function: resolver
render: native
title: UI Kit 2 Test
function:
- key: resolver
handler: index.handler
resources:
- key: main
path: customUI/ui-kit-2/main.js
app:
id: ari:cloud:ecosystem::app/ |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I have merged experimental support for UI Kit 2 which includes a modified |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
The idea is to support UI Kit 2 front-end projects. These work very similar to Custom UI React projects, and if they are written in Typescript, we should compile them to JS before passing them as a build artifact to Forge.
The main work to be done here is quite minimal and includes replacing Custom UI/Custom UIs terms throughout the project with the more generic Resource/Resources terms. For example, today, by default, the plugin generates Custom UI dependencies into a folder called customUI. This and the associated build executor option must be changed to
resources.To be explored is if we could provide a generator configuring UI Kit 2 projects based on the React app generator.
Beta Was this translation helpful? Give feedback.
All reactions