Skip to content

Migrate UI provider guards to capability checks #413

@dgershman

Description

@dgershman

Follow-up to #410 / ADR 0005.

Two UI sites today hide buttons by checking session.provider == .github:

  • Sources/Crow/Views/SessionDetailView.swift:176
  • Sources/Crow/Views/SessionListView.swift:303

With TaskCapability / CodeCapability in place, the view models should
expose capability flags and the views key off those instead. UI should not
need to know about specific providers.

Acceptance

  • Both sites use capability-driven visibility (e.g. viewModel.canSetProjectStatus)
    rather than provider equality.
  • New capability accessors in view models are tested.

References:

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions