Due to the update of UI kit I update my sample forge apps.
For those which are using ConfigForm there are some issues.
E.g. Forge World Time
Pls have a look at the code
After npm install @forge/ui@latest forge deploy echoes the following errors:
[tsl] ERROR in D:\WorldTime\src\WorldClock.tsx(1,70)
TS2614: Module ‘“…/node_modules/@forge/ui/out”’ has no exported member ‘ConfigForm’. Did you mean to use ‘import ConfigForm from “…/node_modules/@forge/ui/out”’ instead?
[tsl] ERROR in D:\WorldTime\src\WorldClock.tsx(45,5)
TS2322: Type ‘{ app: Element; config: Element; defaultConfig: { tz: string; format: string; }; }’ is not assignable to type ‘IntrinsicAttributes & { app: ForgeElement<Record<string, any>>; }’.
Property ‘config’ does not exist on type ‘IntrinsicAttributes & { app: ForgeElement<Record<string, any>>; }’.
Hi @FranzBinder, you may be experiencing a bug with macro config that was recently deployed and discovered. We are investigating the issue now and will give you an update as soon as possible!
Hi @FranzBinder, we’re releasing a fix now. Given that UI Kit is still in beta, we’ve decided to release through a slightly accelerated release process, rather than immediately and risk introducing broken or unreliable code to Confluence, or otherwise interfere with unrelated releases. As such, you should be able to expect the fix to reach production in ~15 hours, barring any major blockers in the release pipeline.
I will be back on Monday morning Sydney time to confirm!
Hi @kchan,
thanks for working on that swiftly!
Did you already deployed the bug fix?
I couldn’t see any change in the behaviour even. Do I need to run forge deploy again?
I too am seeing issues with the config form not preserving values. Can you confirm this bug fix is now deployed to production and the steps required to see this fix with deployed apps.
I’ve just checked the Confluence release pipeline, and it looks like there was an unrelated revert in Confluence over the weekend, which has meant our fix was removed from production for the meantime, in order to fix an issue elsewhere.
The release pipeline is looking stable once more, and the next release with the fix is once again going through the final stages of the release process, which will resume during PST daytime when most of the Confluence team is online. Barring any further Confluence issues, which is highly unlikely, the fix will be in production by 1pm on Monday PST / 8am on Tuesday AEST.
The fix has been included in the latest release to production, so you should be able to use macro configuration in newly created macros again. Thank you for your patience, we’re really sorry for the inconvenience this bug may have caused you.
I tested it with 2 small macros and it worked after forge depoy usage .
The config parameter is accepted and the macro will be render with the new value after:
pressing ENTER inside the config field
or
leaving the config field (e.g. to the next field or to the page body)
@TomNoble, thanks for trying again. I created an app with your code and it seems to work.
I open the edit page, click the pencil button, enter some text into the textfield, click away from the textfield, and the app on the page updates with the text I entered into the textfield.