Let the order of Air Traffic Control rules decide which one wins

Open
#935 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 2 days

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
35/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
swift
Domain
design, desktop

Research direction

Pull request #858 already implements rule reordering and matching, including precedence for existing lists. Read that pull request to understand the current implementation; this issue asks for an off-by-default setting and footer text under the rules list. Done means the setting and proposed footer are added while preserving the stated default behavior.

Written by the indexing model from the issue text.

Description

area: spaces Polish proposal
The problem

With many Air Traffic Control rules, the list in Settings › Spaces gets hard to manage. Rules show in the order I added them, and I can't move them.

This is not a feature in Arc.

What you'd like

As a setting, off by default, the list order becomes the priority. For a link, the topmost matching rule wins. You reorder rules by dragging, with the same handles and drag look as the Spaces list.

  • On upgrade, the list starts in today's precedence order, so no link goes somewhere new.
  • A new rule goes to the bottom of the list. You drag it up if it should win.
  • Proposed footer text under the list: "The first matching rule wins. Drag to reorder. Rules override the default."

Before (today, no order):
atc-before-anonymized

After (drag handles):
706875855-fc282549-4782-44c1-9ba7-91cb36c1e271

#858 implements the reordering and the matching: the first matching rule in the list wins, and existing lists start in today's precedence order. The footer text and the setting aren't in it yet.

How you manage today (optional)

Delete and add routes again in order

Yab version (optional)

No response

Dominant language
Swift
Stars
648
Forks
56
Avg merge
21h 14m
Merged PRs (30d)
22

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from yetanotherbrowser/yab

All issues in yetanotherbrowser/yab

Similar issues

More Swift issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.