     }
 
     @objc(aroundPrecision)
-    public var z_aroundPrecision: NSNumber? {
+    public var z_objc_aroundPrecision: NSNumber? {
         get { return Query.toNumber(self.aroundPrecision) }
         set { self.aroundPrecision = newValue?.uintValue }
     }
 
     @objc(minimumAroundRadius)
-    public var z_minimumAroundRadius: NSNumber? {
+    public var z_objc_minimumAroundRadius: NSNumber? {
         get { return Query.toNumber(self.minimumAroundRadius) }
         set { self.minimumAroundRadius = newValue?.uintValue }
     }

    }

    @objc(exactOnSingleWordQuery)
    public var z_exactOnSingleWordQuery: String? {
        get { return exactOnSingleWordQuery?.rawValue }
        set { exactOnSingleWordQuery = newValue == nil ? nil : ExactOnSingleWordQuery(rawValue: newValue!) }
    }

    @objc(alternativesAsExact)
    public var z_alternativesAsExact: [String]? {
        get {
            if let alternativesAsExact = alternativesAsExact {
                return alternativesAsExact.map({ $0.rawValue })

//       documentation.
//
// This way, each platform sees a properties with the right name and the most
// adequate type. The only drawback is the added clutter of the `z_objc_`-prefixed
// properties in Swift.
//
// There is also an edge case for the `aroundRadiusAll` constant, which is not
