Install for my organization and Connect Slack on the Connections table ended on an empty screen with only a Return button. The screen declared a view field (authorizeUrl) but no component, and a frontend step shows only the components it declares. The screen is now an HTML component: one sentence about what happens, a Continue to Slack link to the consent page (same tab, so Slack can return the browser) and the lifetime of the link, read from SlackOAuthState.LIFETIME_SECONDS (10 minutes). After Slack, the callback redirected to /preferences?section=slack, which the host UI does not serve. It returns to /app/preferences?section=slack with &result=connected or &error=<code>. Connecting in an environment without the public URL or the Slack app secrets failed with "IllegalArgumentException (Slack public URL is required)" or "Slack secret unavailable". It is refused before any state is issued with a user-facing message that says Slack is not set up in this environment, which of the two is missing, and the names of the missing environment variables, never a value. The Preferences action still answers with the authorize address as the whole message: core has no redirect field on an action result. qqq-frontend-next opens a message that is only an https address. Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
2.6 KiB
2.6 KiB
Changelog
All notable changes to this project are documented in this file. The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
[Unreleased]
Changed
SlackDeliveryDestinationnow implements the QQQ 4.1 core delivery SPI (com.kingsrook.qqq.backend.core.delivery, qqq#1205) and the producer registers it asslackin the coreDeliveryDestinationsMetaDataregistry; the stand-in SPI copy is removed.SlackPayloadGuarduses coreClassifiedValuesfor field classification andClassifiedValueTokens.changed()for tokenized restricted values (qqq#1142), replacing its stand-in logic.
Fixed
- Install for my organization and Connect Slack on the Connections table ended on an empty screen with only a Return button: the screen declared a view field but no component, and a frontend step shows only its components. The screen is now an HTML component with one sentence about what happens, a Continue to Slack link to the consent page (same tab) and the link's lifetime (10 minutes,
SlackOAuthState.LIFETIME_SECONDS). - After Slack, the callback redirected to
/preferences?section=slack, which the host UI does not serve. It now returns to/app/preferences?section=slackwith&result=connectedor&error=<code>. - Connecting in an environment without the public URL or the Slack app secrets failed with
IllegalArgumentException (Slack public URL is required)orSlack secret unavailable. It is now refused with a user-facing message: "Slack is not set up in this environment", which of the two is missing, and the names of the missing environment variables, never a value. - QBit metadata now reports the Maven artifact version, including release versions, from a filtered properties resource.
Added
- Complete host-neutral in-app help bundle with live labels and core
HelpBundleAssertionscoverage; registered through QQQ 4.1.0-RC.7HelpBundles, replacing the temporary loader. - "Check channels" action on Registered Channels; readiness now writes the channel's Slack name, private, bot is member, archived, purpose and checked time back to the row.
- User group
handleis resolved fromusergroups.listduring readiness (optionalusergroups:readscope) and used in the mention (<!subteam^ID|@handle>). SlackTablesGuardrailTest: every table is used at runtime, seeded or listed as starting empty, and has help.- Design (
docs/DESIGN.md) and the Slack app manifest (docs/slack-app-manifest.yaml). - Repository scaffold per the QRun qbit repository standard:
SlackQBitProducerandSlackQBitConfig.