### New Issue Checklist <!-- Please check the following boxes [ ] -> [x] before submitting your issue. Click the "Preview" tab for better readability. Thanks for reporting this issue! --> - [x] I am not disclosing a [vulnerability](https://github.com/parse-community/parse-server/blob/master/SECURITY.md). - [x] I am not just asking a [question](https://github.com/parse-community/.github/blob/master/SUPPORT.md). - [x] I have searched through [existing issues](https://github.com/parse-community/Parse-SDK-JS/issues?q=is%3Aissue). - [x] I can reproduce the issue with the latest versions of [Parse Server](https://github.com/parse-community/parse-server/releases) and the [Parse JS SDK](https://github.com/parse-community/Parse-SDK-JS/releases). <!-- We don't investigate issues for outdated releases. --> ### Issue Description <!-- What is the specific issue? --> Parse.Schema.addField can accept Pointer|Parse.Relation according to documentation. Both require a targetClass but there's no way to pass this into the addField function. The addField function strips out all but the type from the fieldOptions. ### Steps to reproduce <!-- How can someone else reproduce the issue? --> Try adding a relation or pointer via the Parse.Schema addField function. ### Actual Outcome <!-- What outcome, for example query result, did you get? --> ### Expected Outcome <!-- What outcome, for example query result, did you expect? --> Either update documentation or maybe pass the targetClass through the options object. Client - Parse JS SDK version: `2.19.0`