Skip to content

Merge pull request #467 from ivpn/bugfix/key-rotation-reasserting #1147

Merge pull request #467 from ivpn/bugfix/key-rotation-reasserting

Merge pull request #467 from ivpn/bugfix/key-rotation-reasserting #1147

Triggered via push February 19, 2025 11:21
Status Success
Total duration 29s
Artifacts

swiftlint.yml

on: push
SwiftLint
20s
SwiftLint
Fit to window
Zoom out
Zoom in

Annotations

10 warnings
SwiftLint: IVPNClient/Models/VPNServerList.swift#L93
Cyclomatic Complexity Violation: Function should have complexity 15 or less: currently complexity equals 32 (cyclomatic_complexity)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L66
Nesting Violation: Types should be nested at most 1 level deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L115
Nesting Violation: Types should be nested at most 1 level deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L108
Nesting Violation: Types should be nested at most 1 level deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L115
Nesting Violation: Types should be nested at most 1 level deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L102
Nesting Violation: Types should be nested at most 1 level deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L108
Nesting Violation: Types should be nested at most 1 level deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L115
Nesting Violation: Types should be nested at most 1 level deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L116
Nesting Violation: Statements should be nested at most 5 levels deep (nesting)
SwiftLint: IVPNClient/Models/V2Ray/V2RayConfig.swift#L117
Nesting Violation: Statements should be nested at most 5 levels deep (nesting)