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.

Sign up for GitHub

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

Add note for NSObject bug when using with CocoaPods #71

Closed
wants to merge 1 commit into from
Closed

Add note for NSObject bug when using with CocoaPods #71

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions README.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -1003,6 +1003,8 @@ The rendering of NSObject depends on the actual class:
With support for Objective-C runtime, templates can render object properties: `{{ user.name }}`.

Subclasses can alter this behavior by overriding the `mustacheBox` method of the `MustacheBoxable` protocol. For more information, check the rendering of [Custom Types](#custom-types) below.

Note that when using GRMustache.swift via CocoaPods, you may run into issue [#28](https://github.com/groue/GRMustache.swift/issues/28).


Custom Types
Expand Down Expand Up @@ -1032,6 +1034,7 @@ When extracting values from your NSObject subclasses, GRMustache.swift uses the

Subclasses can alter this default behavior by overriding the `mustacheBox` method of the `MustacheBoxable` protocol, described below:

Note that when using GRMustache.swift via CocoaPods, you may run into issue [#28](https://github.com/groue/GRMustache.swift/issues/28).

### Pure Swift Values and MustacheBoxable

Expand Down