parse-community / parse-community/docs
📙Little explanation about PFObject Subclassing
Nobody has claimed this yet.
- Dominant language
- SCSS
- Stars
- 317
- Forks
- 507
- PR merge metrics
- No merged PRs in 30d
Description
There is a section regarding how to do Subclassing, it appears to have missing code example.
https://docs.parseplatform.org/ios/guide/#subclasses
PFObject supports dynamic synthesizers just like NSManagedObject. Declare a property as you normally would, but use @dynamic rather than @synthesize in your .m file. The following example creates a displayName property in the Armor class:
And then.. there is no code block.
Also, it wouldn't hurt extending a little bit more on how to do Subclassing properly, Stackoverflow if filled with lot's of different implementations and hacks.
Thanks you for maintaining the project. 👏
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the Subclasses section of the linked iOS Guide page and inspect the text around the sentence introducing the Armor displayName property. Restore the missing Objective-C example and expand the subsection with accurate subclassing guidance; the work is done when the example renders and the section clearly explains the supported approach.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- ios, objective-c
- Domain
- documentation, mobile-dev
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100