github-starred/actual
2
0
Fork 0
mirror of https://github.com/actualbudget/actual.git synced 2026-05-07 20:38:54 -05:00
Code Issues 1.6k Packages Projects Releases 55 Wiki Activity

[GH-ISSUE #6604] oxlint: consistent-type-imports does not enforce import syntax style #28585

New Issue
Closed
opened 2026-04-18 05:21:01 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-04-18 05:21:01 -05:00
Owner
Copy Link

Originally created by @miski-h on GitHub (Jan 8, 2026).
Original GitHub issue: https://github.com/actualbudget/actual/issues/6604

Verified feature request does not already exist?

  • I have searched and found no existing issue

💻

  • Would you like to implement this feature?

Pitch: what problem are you trying to solve?

While working on PR #6557 and issue #6548 , I tested enforcing consistent TypeScript type import
syntax using oxlint’s @typescript-eslint/consistent-type-imports rule.

Currently, both of the following forms are allowed and pass CI:

  • import type { Foo } from '...';
  • import { type Foo } from '...';

Promoting the rule from warn to error does not change this behavior.
As a result, the rule enforces type-only imports vs value imports, but does not enforce a single import syntax style.

If the project intends to standardize on one syntax, this may require either:

  • a different rule, or
  • a missing feature / bug fix in oxlint.

Opening this issue to track the finding after closing PR #6557.

Describe your ideal solution to this problem

No response

Teaching and learning

No response

Originally created by @miski-h on GitHub (Jan 8, 2026). Original GitHub issue: https://github.com/actualbudget/actual/issues/6604 ### Verified feature request does not already exist? - [x] I have searched and found no existing issue ### 💻 - [ ] Would you like to implement this feature? ### Pitch: what problem are you trying to solve? While working on PR #6557 and issue #6548 , I tested enforcing consistent TypeScript type import syntax using oxlint’s `@typescript-eslint/consistent-type-imports` rule. Currently, both of the following forms are allowed and pass CI: - `import type { Foo } from '...';` - `import { type Foo } from '...';` Promoting the rule from `warn` to `error` does not change this behavior. As a result, the rule enforces type-only imports vs value imports, but does not enforce a single import syntax style. If the project intends to standardize on one syntax, this may require either: - a different rule, or - a missing feature / bug fix in oxlint. Opening this issue to track the finding after closing PR #6557. ### Describe your ideal solution to this problem _No response_ ### Teaching and learning _No response_
GiteaMirror commented 2026-04-18 05:21:03 -05:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Jan 8, 2026):

✨ Thanks for sharing your idea! ✨

This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution).

The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+

Don't forget to upvote the top comment with 👍!

<!-- gh-comment-id:3724578408 --> @github-actions[bot] commented on GitHub (Jan 8, 2026): :sparkles: Thanks for sharing your idea! :sparkles: This repository uses a voting-based system for feature requests. While enhancement issues are automatically closed, we still welcome feature requests! The voting system helps us gauge community interest in potential features. We also encourage community contributions for any feature requests marked as needing votes (just post a comment first so we can help guide you toward a successful contribution). The enhancement backlog can be found here: https://github.com/actualbudget/actual/issues?q=label%3A%22needs+votes%22+sort%3Areactions-%2B1-desc+ Don't forget to upvote the top comment with 👍! <!-- feature-auto-close-comment -->
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
AI generated
API
bank sync
budgeting
bug
can’t replicate
dependencies
docker
documentation
electron
experimental feature
feature
feedback
goal templates
good first issue
help wanted
importers
maintenance
needs info
needs testing
needs triage
needs votes
openid
payees
pull-request
Mirrored from GitHub Pull Request
 regression
reports
responsive
rules
schedules
server
✨ merged
split transactions
tech debt
theme
transaction import
transaction reconciliation
transactions
translations
upstream
user interface
✅ approved
wontfix
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/actual#28585
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?