GRMustache
GRMustache copied to clipboard
v8.0.0
GRMustache v8.0.0 (follow up to PR https://github.com/groue/GRMustache/pull/97)
- [ ] Update documentation
- [ ] Make sure we have Core Data tests.
- [ ] More common tests between GRMustache and GRMustache.swift.
New
- [x] Frameworks for iOS.
- [x] Frameworks for OSX.
- [x] Frameworks for tvOS (in tvOS branch).
- [x] Carthage support.
Fixed
- [x] Issue https://github.com/groue/GRMustache/issues/98
Breaking Changes
- [x] GRMustacheOSX.framework targets OSX 10.9.
- [x] GRMustacheiOS.framework targets iOS 8.0.
- [x] Improved compatibility with GRMustache.swift.
- [x] Shared tests suite with GRMustache.swift.
- [x] Common behavior for standard types
- [x] NSArray only recognizes the
first
,last
andcount
keys. - [x] NSOrderedSet only recognizes the
first
,last
andcount
keys. - [x] NSSet only recognizes the
first
andcount
keys. - [x] NSString only recognizes the
length
key.
- [x] NSArray only recognizes the
- [x] Standard Library
- [x] The standard library is no longer loaded by default.
- [x] New
zip
standard library filter.
- [x] Explicit support for Mustache lambdas.
- [x]
{{#partial}}...{{/partial}}
provides dynamic template inheritance. - [ ] Drop support for
{{#x}}...{{^x}}...{{/x}}
short syntax. - [x]
+[GRMustacheTemplate templateFromString:error:]
does no longer look for partials in main bundle's resources.
- [x] The new protocol GRMustacheKeyValueCoding replaces GRMustacheSafeKeyAccess (fixes #66 for good).
- [x] No more support for "unsafe" contexts.
- [x] GRMustache no longer uses
objectForKeyedSubscript:
for objects that respond to this protocol. This behavior now requires explicit conformance to GRMustacheKeyValueCoding.
@marcpalmer @danielphillips: the 8.0.0 release is coming shortly. Yet the Framework branch is Carthage-ready: you can reference it right away from your Cartfile:
github "groue/GRMustache" "Framework"
Using the framework branch currently. Any idea when the 8.0.0 release will be done?
I've been lazy recently, i'm sorry. I'll try to make it this week-end. The longest remaining part is actually updating the documentation.
Anything I can do to help get v8 out the door? I just noticed I'm still pointing to the framework branch which is undesirable.
Thanks for your help proposal, @danielphillips. Let me gather my thoughts.
Hi @groue, can I do anything to help? 8.0.0 looks great
Small question:
Drop support for {{#x}}...{{^x}}...{{/x}} short syntax.
Is there a specific reason that you are thinking of dropping the short syntax? I'm using it in my project at the moment.