2015-08-06 22:44:15 +00:00
|
|
|
/**
|
|
|
|
* Copyright (c) 2015-present, Facebook, Inc.
|
|
|
|
* All rights reserved.
|
|
|
|
*
|
|
|
|
* This source code is licensed under the BSD-style license found in the
|
|
|
|
* LICENSE file in the root directory of this source tree. An additional grant
|
|
|
|
* of patent rights can be found in the PATENTS file in the same directory.
|
|
|
|
*/
|
|
|
|
|
|
|
|
#import "RCTComponentData.h"
|
|
|
|
|
|
|
|
#import <objc/message.h>
|
|
|
|
|
|
|
|
#import "RCTBridge.h"
|
|
|
|
#import "RCTShadowView.h"
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
#import "RCTUtils.h"
|
2015-08-06 22:44:15 +00:00
|
|
|
#import "RCTViewManager.h"
|
2015-11-14 18:25:00 +00:00
|
|
|
#import "UIView+React.h"
|
2015-08-06 22:44:15 +00:00
|
|
|
|
|
|
|
typedef void (^RCTPropBlock)(id<RCTComponent> view, id json);
|
|
|
|
|
|
|
|
@interface RCTComponentProp : NSObject
|
|
|
|
|
|
|
|
@property (nonatomic, copy, readonly) NSString *type;
|
|
|
|
@property (nonatomic, copy) RCTPropBlock propBlock;
|
|
|
|
|
|
|
|
@end
|
|
|
|
|
|
|
|
@implementation RCTComponentProp
|
|
|
|
|
|
|
|
- (instancetype)initWithType:(NSString *)type
|
|
|
|
{
|
|
|
|
if ((self = [super init])) {
|
|
|
|
_type = [type copy];
|
|
|
|
}
|
|
|
|
return self;
|
|
|
|
}
|
|
|
|
|
|
|
|
@end
|
|
|
|
|
|
|
|
@implementation RCTComponentData
|
|
|
|
{
|
|
|
|
id<RCTComponent> _defaultView;
|
|
|
|
RCTShadowView *_defaultShadowView;
|
2015-11-14 18:25:00 +00:00
|
|
|
NSMutableDictionary<NSString *, RCTPropBlock> *_viewPropBlocks;
|
|
|
|
NSMutableDictionary<NSString *, RCTPropBlock> *_shadowPropBlocks;
|
2015-11-25 11:09:00 +00:00
|
|
|
RCTBridge *_bridge;
|
2015-08-06 22:44:15 +00:00
|
|
|
}
|
|
|
|
|
2015-11-25 11:09:00 +00:00
|
|
|
@synthesize manager = _manager;
|
|
|
|
|
|
|
|
- (instancetype)initWithManagerClass:(Class)managerClass
|
|
|
|
bridge:(RCTBridge *)bridge
|
2015-08-06 22:44:15 +00:00
|
|
|
{
|
|
|
|
if ((self = [super init])) {
|
2015-11-25 11:09:00 +00:00
|
|
|
_bridge = bridge;
|
|
|
|
_managerClass = managerClass;
|
2015-08-17 14:35:34 +00:00
|
|
|
_viewPropBlocks = [NSMutableDictionary new];
|
|
|
|
_shadowPropBlocks = [NSMutableDictionary new];
|
2015-08-06 22:44:15 +00:00
|
|
|
|
2015-11-25 11:09:00 +00:00
|
|
|
_name = RCTBridgeModuleNameForClass(_managerClass);
|
2015-08-06 22:44:15 +00:00
|
|
|
RCTAssert(_name.length, @"Invalid moduleName '%@'", _name);
|
|
|
|
if ([_name hasSuffix:@"Manager"]) {
|
|
|
|
_name = [_name substringToIndex:_name.length - @"Manager".length];
|
|
|
|
}
|
|
|
|
}
|
|
|
|
return self;
|
|
|
|
}
|
|
|
|
|
2015-11-25 11:09:00 +00:00
|
|
|
- (RCTViewManager *)manager
|
|
|
|
{
|
|
|
|
if (!_manager) {
|
|
|
|
_manager = [_bridge moduleForClass:_managerClass];
|
|
|
|
}
|
|
|
|
return _manager;
|
|
|
|
}
|
|
|
|
|
2015-08-24 10:14:33 +00:00
|
|
|
RCT_NOT_IMPLEMENTED(- (instancetype)init)
|
2015-08-06 22:44:15 +00:00
|
|
|
|
2015-11-14 18:25:00 +00:00
|
|
|
- (UIView *)createViewWithTag:(NSNumber *)tag props:(NSDictionary<NSString *, id> *)props
|
2015-08-06 22:44:15 +00:00
|
|
|
{
|
|
|
|
RCTAssertMainThread();
|
|
|
|
|
2015-11-25 11:09:00 +00:00
|
|
|
UIView *view = (UIView *)(props ? [self.manager viewWithProps:props] : [_manager view]);
|
2015-08-06 22:44:15 +00:00
|
|
|
view.reactTag = tag;
|
2015-11-14 18:25:00 +00:00
|
|
|
view.multipleTouchEnabled = YES;
|
|
|
|
view.userInteractionEnabled = YES; // required for touch handling
|
|
|
|
view.layer.allowsGroupOpacity = YES; // required for touch handling
|
2015-08-06 22:44:15 +00:00
|
|
|
return view;
|
|
|
|
}
|
|
|
|
|
|
|
|
- (RCTShadowView *)createShadowViewWithTag:(NSNumber *)tag
|
|
|
|
{
|
2015-11-25 11:09:00 +00:00
|
|
|
RCTShadowView *shadowView = [self.manager shadowView];
|
2015-08-06 22:44:15 +00:00
|
|
|
shadowView.reactTag = tag;
|
|
|
|
shadowView.viewName = _name;
|
|
|
|
return shadowView;
|
|
|
|
}
|
|
|
|
|
|
|
|
- (RCTPropBlock)propBlockForKey:(NSString *)name defaultView:(id)defaultView
|
|
|
|
{
|
|
|
|
BOOL shadowView = [defaultView isKindOfClass:[RCTShadowView class]];
|
2015-11-14 18:25:00 +00:00
|
|
|
NSMutableDictionary<NSString *, RCTPropBlock> *propBlocks = shadowView ? _shadowPropBlocks : _viewPropBlocks;
|
2015-08-06 22:44:15 +00:00
|
|
|
RCTPropBlock propBlock = propBlocks[name];
|
|
|
|
if (!propBlock) {
|
|
|
|
|
|
|
|
__weak RCTComponentData *weakSelf = self;
|
|
|
|
|
|
|
|
// Get type
|
|
|
|
SEL type = NULL;
|
|
|
|
NSString *keyPath = nil;
|
|
|
|
SEL selector = NSSelectorFromString([NSString stringWithFormat:@"propConfig%@_%@", shadowView ? @"Shadow" : @"", name]);
|
|
|
|
Class managerClass = [_manager class];
|
|
|
|
if ([managerClass respondsToSelector:selector]) {
|
2015-11-03 22:45:46 +00:00
|
|
|
NSArray<NSString *> *typeAndKeyPath =
|
|
|
|
((NSArray<NSString *> *(*)(id, SEL))objc_msgSend)(managerClass, selector);
|
2015-08-06 22:44:15 +00:00
|
|
|
type = NSSelectorFromString([typeAndKeyPath[0] stringByAppendingString:@":"]);
|
|
|
|
keyPath = typeAndKeyPath.count > 1 ? typeAndKeyPath[1] : nil;
|
|
|
|
} else {
|
|
|
|
propBlock = ^(__unused id view, __unused id json) {};
|
|
|
|
propBlocks[name] = propBlock;
|
|
|
|
return propBlock;
|
|
|
|
}
|
|
|
|
|
|
|
|
// Check for custom setter
|
|
|
|
if ([keyPath isEqualToString:@"__custom__"]) {
|
|
|
|
|
|
|
|
// Get custom setter
|
|
|
|
SEL customSetter = NSSelectorFromString([NSString stringWithFormat:@"set_%@:for%@View:withDefaultView:", name, shadowView ? @"Shadow" : @""]);
|
|
|
|
|
|
|
|
propBlock = ^(id<RCTComponent> view, id json) {
|
|
|
|
((void (*)(id, SEL, id, id, id))objc_msgSend)(
|
|
|
|
weakSelf.manager, customSetter, json == (id)kCFNull ? nil : json, view, defaultView
|
|
|
|
);
|
|
|
|
};
|
|
|
|
|
|
|
|
} else {
|
|
|
|
|
|
|
|
// Disect keypath
|
|
|
|
NSString *key = name;
|
2015-11-03 22:45:46 +00:00
|
|
|
NSArray<NSString *> *parts = [keyPath componentsSeparatedByString:@"."];
|
2015-08-06 22:44:15 +00:00
|
|
|
if (parts) {
|
2015-08-24 10:14:33 +00:00
|
|
|
key = parts.lastObject;
|
2015-08-06 22:44:15 +00:00
|
|
|
parts = [parts subarrayWithRange:(NSRange){0, parts.count - 1}];
|
|
|
|
}
|
|
|
|
|
|
|
|
// Get property getter
|
|
|
|
SEL getter = NSSelectorFromString(key);
|
|
|
|
|
|
|
|
// Get property setter
|
|
|
|
SEL setter = NSSelectorFromString([NSString stringWithFormat:@"set%@%@:",
|
2015-08-24 10:14:33 +00:00
|
|
|
[key substringToIndex:1].uppercaseString,
|
2015-08-06 22:44:15 +00:00
|
|
|
[key substringFromIndex:1]]);
|
|
|
|
|
|
|
|
// Build setter block
|
|
|
|
void (^setterBlock)(id target, id source, id json) = nil;
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
if (type == NSSelectorFromString(@"RCTBubblingEventBlock:") ||
|
|
|
|
type == NSSelectorFromString(@"RCTDirectEventBlock:")) {
|
|
|
|
|
|
|
|
// Special case for event handlers
|
|
|
|
__weak RCTViewManager *weakManager = _manager;
|
|
|
|
setterBlock = ^(id target, __unused id source, id json) {
|
|
|
|
__weak id<RCTComponent> weakTarget = target;
|
|
|
|
((void (*)(id, SEL, id))objc_msgSend)(target, setter, [RCTConvert BOOL:json] ? ^(NSDictionary *body) {
|
|
|
|
body = [NSMutableDictionary dictionaryWithDictionary:body];
|
|
|
|
((NSMutableDictionary *)body)[@"target"] = weakTarget.reactTag;
|
|
|
|
[weakManager.bridge.eventDispatcher sendInputEventWithName:RCTNormalizeInputEventName(name) body:body];
|
|
|
|
} : nil);
|
|
|
|
};
|
|
|
|
|
|
|
|
} else {
|
|
|
|
|
|
|
|
// Ordinary property handlers
|
|
|
|
NSMethodSignature *typeSignature = [[RCTConvert class] methodSignatureForSelector:type];
|
|
|
|
switch (typeSignature.methodReturnType[0]) {
|
|
|
|
|
|
|
|
#define RCT_CASE(_value, _type) \
|
|
|
|
case _value: { \
|
|
|
|
_type (*convert)(id, SEL, id) = (typeof(convert))objc_msgSend; \
|
|
|
|
_type (*get)(id, SEL) = (typeof(get))objc_msgSend; \
|
|
|
|
void (*set)(id, SEL, _type) = (typeof(set))objc_msgSend; \
|
|
|
|
setterBlock = ^(id target, id source, id json) { \
|
|
|
|
set(target, setter, json ? convert([RCTConvert class], type, json) : get(source, getter)); \
|
|
|
|
}; \
|
|
|
|
break; \
|
|
|
|
}
|
|
|
|
|
|
|
|
RCT_CASE(_C_SEL, SEL)
|
|
|
|
RCT_CASE(_C_CHARPTR, const char *)
|
|
|
|
RCT_CASE(_C_CHR, char)
|
|
|
|
RCT_CASE(_C_UCHR, unsigned char)
|
|
|
|
RCT_CASE(_C_SHT, short)
|
|
|
|
RCT_CASE(_C_USHT, unsigned short)
|
|
|
|
RCT_CASE(_C_INT, int)
|
|
|
|
RCT_CASE(_C_UINT, unsigned int)
|
|
|
|
RCT_CASE(_C_LNG, long)
|
|
|
|
RCT_CASE(_C_ULNG, unsigned long)
|
|
|
|
RCT_CASE(_C_LNG_LNG, long long)
|
|
|
|
RCT_CASE(_C_ULNG_LNG, unsigned long long)
|
|
|
|
RCT_CASE(_C_FLT, float)
|
|
|
|
RCT_CASE(_C_DBL, double)
|
|
|
|
RCT_CASE(_C_BOOL, BOOL)
|
|
|
|
RCT_CASE(_C_PTR, void *)
|
|
|
|
RCT_CASE(_C_ID, id)
|
|
|
|
|
|
|
|
case _C_STRUCT_B:
|
|
|
|
default: {
|
|
|
|
|
|
|
|
NSInvocation *typeInvocation = [NSInvocation invocationWithMethodSignature:typeSignature];
|
|
|
|
typeInvocation.selector = type;
|
|
|
|
typeInvocation.target = [RCTConvert class];
|
|
|
|
|
|
|
|
__block NSInvocation *sourceInvocation = nil;
|
|
|
|
__block NSInvocation *targetInvocation = nil;
|
|
|
|
|
|
|
|
setterBlock = ^(id target, id source, id json) { \
|
|
|
|
|
|
|
|
// Get value
|
|
|
|
void *value = malloc(typeSignature.methodReturnLength);
|
|
|
|
if (json) {
|
|
|
|
[typeInvocation setArgument:&json atIndex:2];
|
|
|
|
[typeInvocation invoke];
|
|
|
|
[typeInvocation getReturnValue:value];
|
|
|
|
} else {
|
|
|
|
if (!sourceInvocation && source) {
|
|
|
|
NSMethodSignature *signature = [source methodSignatureForSelector:getter];
|
|
|
|
sourceInvocation = [NSInvocation invocationWithMethodSignature:signature];
|
|
|
|
sourceInvocation.selector = getter;
|
|
|
|
}
|
|
|
|
[sourceInvocation invokeWithTarget:source];
|
|
|
|
[sourceInvocation getReturnValue:value];
|
|
|
|
}
|
2015-08-06 22:44:15 +00:00
|
|
|
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
// Set value
|
|
|
|
if (!targetInvocation && target) {
|
|
|
|
NSMethodSignature *signature = [target methodSignatureForSelector:setter];
|
|
|
|
targetInvocation = [NSInvocation invocationWithMethodSignature:signature];
|
|
|
|
targetInvocation.selector = setter;
|
2015-08-06 22:44:15 +00:00
|
|
|
}
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
[targetInvocation setArgument:value atIndex:2];
|
|
|
|
[targetInvocation invokeWithTarget:target];
|
|
|
|
free(value);
|
|
|
|
};
|
|
|
|
break;
|
|
|
|
}
|
2015-08-06 22:44:15 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
propBlock = ^(__unused id view, __unused id json) {
|
|
|
|
|
|
|
|
// Follow keypath
|
|
|
|
id target = view;
|
|
|
|
for (NSString *part in parts) {
|
|
|
|
target = [target valueForKey:part];
|
|
|
|
}
|
|
|
|
|
|
|
|
if (json == (id)kCFNull) {
|
|
|
|
|
|
|
|
// Copy default property
|
|
|
|
id source = defaultView;
|
|
|
|
for (NSString *part in parts) {
|
|
|
|
source = [source valueForKey:part];
|
|
|
|
}
|
|
|
|
setterBlock(target, source, nil);
|
|
|
|
|
|
|
|
} else {
|
|
|
|
|
|
|
|
// Set property with json
|
|
|
|
setterBlock(target, nil, json);
|
|
|
|
}
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
|
|
|
if (RCT_DEBUG) {
|
|
|
|
|
|
|
|
// Provide more useful log feedback if there's an error
|
|
|
|
RCTPropBlock unwrappedBlock = propBlock;
|
|
|
|
propBlock = ^(id<RCTComponent> view, id json) {
|
|
|
|
NSString *logPrefix = [NSString stringWithFormat:
|
|
|
|
@"Error setting property '%@' of %@ with tag #%@: ",
|
|
|
|
name, weakSelf.name, view.reactTag];
|
|
|
|
|
|
|
|
RCTPerformBlockWithLogPrefix(^{ unwrappedBlock(view, json); }, logPrefix);
|
|
|
|
};
|
|
|
|
}
|
|
|
|
|
|
|
|
propBlocks[name] = [propBlock copy];
|
|
|
|
}
|
|
|
|
return propBlock;
|
|
|
|
}
|
|
|
|
|
2015-11-14 18:25:00 +00:00
|
|
|
- (void)setProps:(NSDictionary<NSString *, id> *)props forView:(id<RCTComponent>)view
|
2015-08-06 22:44:15 +00:00
|
|
|
{
|
|
|
|
if (!view) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!_defaultView) {
|
2015-08-25 14:45:07 +00:00
|
|
|
_defaultView = [self createViewWithTag:nil props:nil];
|
2015-08-06 22:44:15 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
[props enumerateKeysAndObjectsUsingBlock:^(NSString *key, id json, __unused BOOL *stop) {
|
|
|
|
[self propBlockForKey:key defaultView:_defaultView](view, json);
|
|
|
|
}];
|
|
|
|
}
|
|
|
|
|
2015-11-14 18:25:00 +00:00
|
|
|
- (void)setProps:(NSDictionary<NSString *, id> *)props forShadowView:(RCTShadowView *)shadowView
|
2015-08-06 22:44:15 +00:00
|
|
|
{
|
|
|
|
if (!shadowView) {
|
|
|
|
return;
|
|
|
|
}
|
|
|
|
|
|
|
|
if (!_defaultShadowView) {
|
|
|
|
_defaultShadowView = [self createShadowViewWithTag:nil];
|
|
|
|
}
|
|
|
|
|
|
|
|
[props enumerateKeysAndObjectsUsingBlock:^(NSString *key, id json, __unused BOOL *stop) {
|
|
|
|
[self propBlockForKey:key defaultView:_defaultShadowView](shadowView, json);
|
|
|
|
}];
|
|
|
|
|
|
|
|
[shadowView updateLayout];
|
|
|
|
}
|
|
|
|
|
2015-11-14 18:25:00 +00:00
|
|
|
- (NSDictionary<NSString *, id> *)viewConfig
|
2015-08-06 22:44:15 +00:00
|
|
|
{
|
2015-11-03 22:45:46 +00:00
|
|
|
NSMutableArray<NSString *> *directEvents = [NSMutableArray new];
|
2015-11-25 11:09:00 +00:00
|
|
|
if (RCTClassOverridesInstanceMethod(_managerClass, @selector(customDirectEventTypes))) {
|
|
|
|
NSArray<NSString *> *events = [self.manager customDirectEventTypes];
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
if (RCT_DEBUG) {
|
|
|
|
RCTAssert(!events || [events isKindOfClass:[NSArray class]],
|
|
|
|
@"customDirectEventTypes must return an array, but %@ returned %@",
|
2015-11-25 11:09:00 +00:00
|
|
|
_managerClass, [events class]);
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
}
|
|
|
|
for (NSString *event in events) {
|
|
|
|
[directEvents addObject:RCTNormalizeInputEventName(event)];
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
2015-11-03 22:45:46 +00:00
|
|
|
NSMutableArray<NSString *> *bubblingEvents = [NSMutableArray new];
|
2015-11-25 11:09:00 +00:00
|
|
|
if (RCTClassOverridesInstanceMethod(_managerClass, @selector(customBubblingEventTypes))) {
|
|
|
|
NSArray<NSString *> *events = [self.manager customBubblingEventTypes];
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
if (RCT_DEBUG) {
|
|
|
|
RCTAssert(!events || [events isKindOfClass:[NSArray class]],
|
|
|
|
@"customBubblingEventTypes must return an array, but %@ returned %@",
|
2015-11-25 11:09:00 +00:00
|
|
|
_managerClass, [events class]);
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
}
|
|
|
|
for (NSString *event in events) {
|
|
|
|
[bubblingEvents addObject:RCTNormalizeInputEventName(event)];
|
|
|
|
}
|
|
|
|
}
|
2015-08-06 22:44:15 +00:00
|
|
|
|
|
|
|
unsigned int count = 0;
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
NSMutableDictionary *propTypes = [NSMutableDictionary new];
|
2015-11-25 11:09:00 +00:00
|
|
|
Method *methods = class_copyMethodList(object_getClass(_managerClass), &count);
|
2015-08-06 22:44:15 +00:00
|
|
|
for (unsigned int i = 0; i < count; i++) {
|
|
|
|
Method method = methods[i];
|
|
|
|
SEL selector = method_getName(method);
|
|
|
|
NSString *methodName = NSStringFromSelector(selector);
|
|
|
|
if ([methodName hasPrefix:@"propConfig"]) {
|
|
|
|
NSRange nameRange = [methodName rangeOfString:@"_"];
|
|
|
|
if (nameRange.length) {
|
|
|
|
NSString *name = [methodName substringFromIndex:nameRange.location + 1];
|
2015-11-25 11:09:00 +00:00
|
|
|
NSString *type = ((NSArray<NSString *> *(*)(id, SEL))objc_msgSend)(_managerClass, selector)[0];
|
2015-08-06 22:44:15 +00:00
|
|
|
if (RCT_DEBUG && propTypes[name] && ![propTypes[name] isEqualToString:type]) {
|
|
|
|
RCTLogError(@"Property '%@' of component '%@' redefined from '%@' "
|
|
|
|
"to '%@'", name, _name, propTypes[name], type);
|
|
|
|
}
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
|
|
|
|
if ([type isEqualToString:@"RCTBubblingEventBlock"]) {
|
|
|
|
[bubblingEvents addObject:RCTNormalizeInputEventName(name)];
|
|
|
|
propTypes[name] = @"BOOL";
|
|
|
|
} else if ([type isEqualToString:@"RCTDirectEventBlock"]) {
|
|
|
|
[directEvents addObject:RCTNormalizeInputEventName(name)];
|
|
|
|
propTypes[name] = @"BOOL";
|
|
|
|
} else {
|
|
|
|
propTypes[name] = type;
|
|
|
|
}
|
2015-08-06 22:44:15 +00:00
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
free(methods);
|
|
|
|
|
Added mechanism for directly mapping JS event handlers to blocks
Summary:
Currently, the system for mapping JS event handlers to blocks is quite clean on the JS side, but is clunky on the native side. The event property is passed as a boolean, which can then be checked by the native side, and if true, the native side is supposed to send an event via the event dispatcher.
This diff adds the facility to declare the property as a block instead. This means that the event side can simply call the block, and it will automatically send the event. Because the blocks for bubbling and direct events are named differently, we can also use this to generate the event registration data and get rid of the arrays of event names.
The name of the event is inferred from the property name, which means that the property for an event called "load" must be called `onLoad` or the mapping won't work. This can be optionally remapped to a different property name on the view itself if necessary, e.g.
RCT_REMAP_VIEW_PROPERTY(onLoad, loadEventBlock, RCTDirectEventBlock)
If you don't want to use this mechanism then for now it is still possible to declare the property as a BOOL instead and use the old mechanism (this approach is now deprecated however, and may eventually be removed altogether).
2015-09-02 12:58:10 +00:00
|
|
|
if (RCT_DEBUG) {
|
|
|
|
for (NSString *event in directEvents) {
|
|
|
|
if ([bubblingEvents containsObject:event]) {
|
|
|
|
RCTLogError(@"Component '%@' registered '%@' as both a bubbling event "
|
|
|
|
"and a direct event", _name, event);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
for (NSString *event in bubblingEvents) {
|
|
|
|
if ([directEvents containsObject:event]) {
|
|
|
|
RCTLogError(@"Component '%@' registered '%@' as both a bubbling event "
|
|
|
|
"and a direct event", _name, event);
|
|
|
|
}
|
|
|
|
}
|
|
|
|
}
|
|
|
|
|
|
|
|
return @{
|
|
|
|
@"propTypes" : propTypes,
|
|
|
|
@"directEvents" : directEvents,
|
|
|
|
@"bubblingEvents" : bubblingEvents,
|
|
|
|
};
|
2015-08-06 22:44:15 +00:00
|
|
|
}
|
|
|
|
|
|
|
|
@end
|