ParseFile init without previous fetch

cbaker6 · October 17, 2021, 2:15pm

I don’t fully understand your question, but a ParseFile along with ParseObject is Encodable and Decodable via:

parse-community/Parse-Swift/blob/aeb363f552fc80477db4685627f94c64de00c87c/Sources/ParseSwift/Protocols/Fileable.swift#L11

    
      
          //
          //  Fileable.swift
          //  ParseSwift
          //
          //  Created by Corey Baker on 12/27/20.
          //  Copyright © 2020 Parse Community. All rights reserved.
          //
          
          
import Foundation
          
          
protocol Fileable: ParseType, Decodable, Identifiable {
              var __type: String { get } // swiftlint:disable:this identifier_name
              var name: String { get set }
              var url: URL? { get set }
          }
          
          
extension Fileable {
              var isSaved: Bool {
                  return url != nil
              }

Every ParseObject allows you to retrieve the proper encoded form with the className prepended using description or debugDescription:

github.com

parse-community/Parse-Swift/blob/aeb363f552fc80477db4685627f94c64de00c87c/Sources/ParseSwift/Objects/ParseObject.swift#L553-L569

    
      
          extension ParseObject {
              public var debugDescription: String {
                  guard let descriptionData = try? ParseCoding.jsonEncoder().encode(self),
                      let descriptionString = String(data: descriptionData, encoding: .utf8) else {
                          return "\(className) ()"
                  }
          
          
        return "\(className) (\(descriptionString))"
              }
          }
          
          
// MARK: CustomStringConvertible
          extension ParseObject {
              public var description: String {
                  debugDescription
              }
          }

My guess is you are running into issues because your JSON encoder/decoder isn’t configured to handle ParseObject's correctly. I say this because if ParseFile wasn’t encodable/decodable, it would mean you can’t save/retrieve files from a Parse Server, a number of tests on the SDK should have failed, and the Playgrounds wouldn’t work properly. It could also be because you are using Codable which technically ParseTypes are, but they don’t conform to Codable directly. Instead, they are all Encodable and Decodable, not sure if the compiler resolves this for you… To encode any ParseObject or Parse Type, you should be using the included Parse encoders/decoder. These can be accessed by looking at some code from one of my projects:

github.com

netreconlab/ParseCareKit/blob/f84df70575eada8d763c7493d31e9a39f5c387fa/Sources/ParseCareKit/PCKUtility.swift#L98-L111

    
      
          /// Get the current Parse Encoder with custom date strategy.
          public class func encoder() -> ParseEncoder {
              PCKOutcome().getEncoder()
          }
          
          
/// Get the current JSON Encoder with custom date strategy.
          public class func jsonEncoder() -> JSONEncoder {
              PCKOutcome().getJSONEncoder()
          }
          
          
/// Get the current JSON Decoder with custom date strategy.
          public class func decoder() -> JSONDecoder {
              PCKOutcome().getDecoder()
          }

You can use any instance of one of your ParseObject’s as they will all give you the same encoders/decoders. The ones it seems you are interested in are: jsonEncoder and decoder. You shouldn’t use encoder for your local storage is this is the required encoded needed to send objects to the server.