realm / realm/SwiftLint

Rule Request: Alphabetise struct property let / vars.

Open
#5,541 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

rule-request
Dominant language
Swift
Stars
19.7k
Forks
2.3k
Avg merge
1d 1h
Merged PRs (30d)
11

Description

New Issue Checklist
New rule request

Sort let and var propery name alapbetically. However, exclude SwiftUI Views as this would cause an issue with trailing closure syntax. Also id and identifier should be allowed as first items

Triggering:

public struct EmailViewItems: Identifiable {
    public let id = UUID()
    public let button: String
    public let appName: String
    public let address: String

public struct EmailViewItems {
    public let button: String
    public let appName: String
    public let address: String
    public let id = UUID()

Non-triggering:

public struct EmailViewItems: Identifiable {
    public let id = UUID()
    public let appName: String
    public let address: String
    public let button: String

public struct EmailViewItems {
    public let id = UUID()
    public let appName: String
    public let address: String
    public let button: String
    
struct Icon: View {
    private var image: Image
    private var width: CGFloat
    private var height: CGFloat

Contributor guide

Open the contributing guide

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.

Research direction

The issue names no files or tests. Start by locating SwiftLint's existing rule implementations and test conventions, then determine how struct properties and SwiftUI Views are identified; done means the requested ordering, id/identifier exceptions, and SwiftUI exclusion are covered by tests.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.