Skip to content
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

ParseConfig throwing Codable errors when type Object exists in Config. #437

Open
4 tasks done
proj-sashido opened this issue Feb 12, 2023 · 1 comment
Open
4 tasks done
Labels
type:bug Impaired feature or lacking behavior that is likely assumed

Comments

@proj-sashido
Copy link

New Issue Checklist

Issue Description

  • On my ParseServer, in the Config, I have variables that are of type “Object”.
  • I cannot create variables to represent these JSON objects (i.e. Dictionary<String, Any>) into my subclassed ParseConfig class.

Steps to reproduce

  • Create a subclass of ParseConfig
  • Create any variable with type Dictionary<String, Any>? or Dictionary<String, AnyObject>?

Actual Outcome

  • An error saying ParseConfig no longer conforms to Codable, and that I need to add stubs.

Expected Outcome

  • No error

Environment

Client

  • Parse Swift SDK version: 4.14.2
  • Xcode version: Version 14.2 (14C18)
  • Operating system (iOS, macOS, watchOS, etc.): macOS (M2 Pro)
  • Operating system version: Ventura 13.2 (22D49)

Server

  • Parse Server version: 2.3.3
  • Operating system: Unknown
  • Local or remote host (AWS, Azure, Google Cloud, Heroku, Digital Ocean, etc): SashiDo / AWS

Database

  • System (MongoDB or Postgres): MongoDB
  • Database version: Unknown
  • Local or remote host (MongoDB Atlas, mLab, AWS, Azure, Google Cloud, etc): Unknown
@parse-github-assistant
Copy link

Thanks for opening this issue!

  • 🚀 You can help us to fix this issue faster by opening a pull request with a failing test. See our Contribution Guide for how to make a pull request, or read our New Contributor's Guide if this is your first time contributing.

@mtrezza mtrezza added the type:bug Impaired feature or lacking behavior that is likely assumed label Feb 13, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:bug Impaired feature or lacking behavior that is likely assumed
Projects
None yet
Development

No branches or pull requests

2 participants