[WilliamBergamin]

Changelog

The features.user_connections app manifest property (is_enabled, auth_hosts) is now supported, so it is kept by run, deploy, and manifest sync.

Summary

The CLI decodes manifest.json (or the get-manifest hook output) into typed manifest structs, so any property it does not model is silently dropped before the manifest is sent to Slack. This adds features.user_connections to AppFeatures so apps that opt into the standardized user connection flow keep that setting.

is_enabled is a pointer, like code_channels.enabled, so an explicit false is kept and a missing value is left for Slack to reject.

Preview

slack manifest info --source local with features.user_connections in manifest.json:

Before (main): the property is stripped

"features": {
  "app_home": {},
  "bot_user": { "display_name": "connector" }
}

After (this branch): the property round-trips

"features": {
  "app_home": {},
  "bot_user": { "display_name": "connector" },
  "user_connections": {
    "is_enabled": true,
    "auth_hosts": ["example.com", "auth.example.com"]
  }
}

Testing

• New cases in Test_AppManifest_AppFeatures for enabled and explicitly disabled user_connections.
• New Test_AppManifest_AppFeatures_UserConnections decodes manifest JSON, asserts the typed value, and checks it re-marshals unchanged (undefined, enabled, disabled with hosts, omitted fields).
• make test passes (lint: 0 issues).
• Manual: built main and this branch, ran slack manifest info --source local on a sample project with the property (output above).

Notes

• Follow-up: add user_connections to slackapi/manifest-schema so editors stop flagging it.
• Host format and item limits are validated by Slack's manifest API, like other manifest properties.

Requirements

• I've read and understood the Contributing Guidelines and have done my best effort to follow them.
• I've read and agree to the Code of Conduct.

🤖 Generated with Claude Code

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 78.14%. Comparing base (06c2fd4) to head (51916c6).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main     #688      +/-   ##
==========================================
+ Coverage   78.11%   78.14%   +0.02%     
==========================================
  Files         239      239              
  Lines       18135    18135              
==========================================
+ Hits        14167    14171       +4     
+ Misses       3968     3964       -4     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[mwbrooks]

Thanks @WilliamBergamin - this matches the code_channels pattern and looks good.

❓ Question: I checked the shape against the manifest schema in the Slack API: is_enabled and auth_hosts both look to be required whenever user_connections is declared. Are you certain that it's safe to is_enabled a pointer and leave validation to Slack?

[mwbrooks]

praise: 👌🏻 omitempty looking good

[mwbrooks]

note: Thanks for calling out that the is_enabled bool is intentionally a pointer because it's an optional param that can fallback on the Slack API default value.

[WilliamBergamin]

@mwbrooks Good question, I checked the schema too: both are required, with no default. That's why is_enabled is a pointer. A plain bool with omitempty would drop an explicit false, and one without it would quietly send false when the field is missing. With *bool, the CLI passes through exactly what the user wrote, and Slack rejects a missing field with missing_field pointing at /features/user_connections 🤔

[mwbrooks]

@mwbrooks Good question, I checked the schema too: both are required, with no default. That's why is_enabled is a pointer. A plain bool with omitempty would drop an explicit false, and one without it would quietly send false when the field is missing. With *bool, the CLI passes through exactly what the user wrote, and Slack rejects a missing field with missing_field pointing at /features/user_connections 🤔

@WilliamBergamin Good point that the manifest validation will enforce it and explain that it's required. I prefer that we keep it as-is with the omitempty so that the JSON is passed through to the API exactly as the user wrote it.