-
Notifications
You must be signed in to change notification settings - Fork 1.4k
Minor Codable conformance improvements in SwiftBuildSupport #8449
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
@swift-ci test |
try super.init(from: decoder) | ||
} | ||
} | ||
|
||
/// Abstract base class for all items in the group hierarchy. | ||
public class Reference: TypedObject { | ||
public class Reference: HighLevelObject { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really a high-level object... but will go away in my next PR.
@@ -693,7 +712,7 @@ public enum PIF { | |||
} | |||
|
|||
/// Abstract base class for all build phases in a target. | |||
public class BuildPhase: TypedObject { | |||
public class BuildPhase: HighLevelObject { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not really a high-level object... but will go away in my next PR.
@swift-ci test |
@swift-ci test windows |
@swift-ci test windows self hosted |
@swift-ci please test self hosted windows |
Motivation:
Some of the
SwiftBuildSupport/PIFBuilder.swift
encoding/decoding code was using unsafe string keys. This replaces with proper typesafe keys.This part of the ground work to support the new PIF builder in
SwiftBuildSupport
(i.e., rdar://147527170).Modifications:
When conforming to
Codable
, replace string keys withenum
based keys instead.Result:
The resulting code is safer and easier to understand.
Tracked by rdar://148546582.