forge lint cannot see your request helper: the Jira scopes it never checks
forge lint cannot see your request helper: the Jira scopes it never checks Key takeaways forge lint only recognises a requestJira call when the endpoint is written inline as a literal, template literal or route`` tag. A path arriving as a variable is dropped silently. One request helper is enough to hide every Atlassian REST call in a codebase. I linted an app needing write:jira-work and…
Forge lint cannot detect request helper calls due to Jira scope limitations. The lint tool only recognizes requestJira calls when the endpoint is written as a literal, template literal, or route tag. However, if the path arrives as a variable—such as when using a request helper—the call is silently dropped. This means that if a developer uses a request helper to perform a requestJira call with an undeclared scope, the lint tool will not report any missing scopes.
This can lead to unexpected 401 Unauthorized errors when the app is deployed, as the tool does not check for missing scopes.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
