← Back to issue list

Create constants for common permissions values

View original Github issue

Metadata

Project
craft-store
Number
#386
Type
issue
State
closed
Author
lengau
Labels
Status: Triaged Type: Enhancement
Created
Updated
Closed

Current evaluation

Permission constants were added and magic strings replaced by merged PR #399 (commit 19166ba), resolving #386.

Resolution: closed resolved

Reason: PR #399 added documented constants for known permissions and fixed #386; it merged as commit 19166ba.

Evaluated by: mr-cal-bot

No scores available.

Issue body

### What needs to get done Create constants to use for common permissions values with the `PublisherGateway`. ### Why it needs to get done Taking strings is yucky.

Evaluation history

Date Model Scores Action Summary
stealth/space-bunny-alpha — closed resolved Permission constants were added and magic strings replaced by merged PR #399 (commit 19166ba), resolving #386.
stealth/space-bunny-alpha — closed stale Closed without a recorded implementation; only automated Jira notices followed, with no linking PR, commit, or release.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The enhancement to replace string literals with constants for PublisherGateway permissions received no pull requests or code changes, indicating the task was deferred or abandoned.
qwen/qwen3.6-35b-a3b — — Closed without implementation. The enhancement to create permission constants for the PublisherGateway was superseded by internal Jira tickets CRAFT-5221 and CRAFT-5222, with no pull request or code changes recorded.

Update history

No update history recorded yet.

Related work

  • Likely Fixed By: canonical/craft-store#399 (confidence 100%)

    Merged PR added known-attenuation constants, replaced magic strings, and explicitly fixed #386.

Related issues

Issue Project State Summary Similarity
#399 feat: add constants for more known attenuations craft-store merged PR #399 by maintainer lengau added constants for more known permission values, replaced magic strings with them, and fixed issue #386. Merged with 2 approvals; only the OSV-scanner check failed.
72%