组件化开发

公司新需求“打卡瓜分奖池”，公司工程又很复杂，功能模块比较多，之前业开发过定数组件、购物车组件等，这次综合组件化开发的优缺点后，再次打算将此需求当做小模块，实行组件化开发。
公司工程实现路由解耦，简单介绍一下：

字符串

NSString *const WishListControllerURL = @"code://WishListController";
NSString *const WriteWishControllerURL = @"xib://WriteWishController";
NSString *const PlanControllerURL  =@"sb://ReadingPlan/DDReadPlanInterestingViewController"

使用方式

[[DDRoute route] pushViewWithURL:WishListControllerURL param:@{@"searchResultControllerURL":@"code://DDSearchBookResultController"}];

1. DDRoute 是个路由管理类。
2. param 是个参数集合，包括block传值。
3. [DDRoute route] 实例化单例，内部有个routeManager属性，保存当前控制器的navVC，pushViewWithURL时，根据url字符串截取出控制器的字符串，转化为控制器class，该类事先遵守个Scheme协议，再实例化目标控制器targetVC，再将参数param 和targetVC 关联，因为targetVC遵守协议Scheme，然后用Scheme调用自身API，将targetVC 传入，该API作用是将targetVC的内部属性和param一一赋值，然后再调用[self.nav push:targetVC]

4. 
           if([view conformsToProtocol:@protocol(Scheme)])
           {
               if ([Scheme validObject:view])
               {
                   if (fold)
                   {
                       NSMutableArray *controllers = [self controllerAfterFold];
                       [controllers addObject:view];
                       [self.navigationController setViewControllers:controllers animated:animated];
                   }
                   else
                   {
                       [self.navigationController pushViewController:view animated:animated];
                   }
               }
           }
           
   

   下面是Scheme内关键代码

   	+ (BOOL)validObject:(NSObject<Scheme>*)object+ (BOOL)validObject:		(NSObject<Scheme>*)object
   {
   if (![object conformsToProtocol:@protocol(Scheme)])
   {
       NSLogInfo(@"%@ not conform to Scheme", object);
       return YES;
   }
   
   NSDictionary *schemes     = [[object class] schemes];
   Class         objectClass = [object class];
   
   if (!schemes)
   {
       NSLogWarn( @"please provide +[%@ paramsSchemes]", NSStringFromClass(objectClass) );
       return YES;
   }
   
   NSDictionary *params = [object params];
   
   return [self validForObject:object
                        params:params
                       schemes:schemes];
   }
   
   + (BOOL)validForObject:(id)object+ (BOOL)validForObject:(id)object
               params:(id)params
              schemes:(NSDictionary*)schemes
   {
   Class objectClass = [object class];
   
   if (!params || ![params isKindOfClass:[NSDictionary class]])
   {
       NSLogError( @"params for %@ not a NSDictionary", NSStringFromClass(objectClass) );
       [[self class] promptUsageForObject:object schemes:schemes];
       return NO;
   }
   
   __block NSString *error = nil;
   
   [schemes enumerateKeysAndObjectsUsingBlock: ^(id key, Scheme *scheme, BOOL *stop) {
       id paramValue = [params valueForKey:key];
   
       if (!paramValue && !scheme.optional)
       {
           error = [NSString stringWithFormat:@"miss %@", key];
           NSLogError(@"%@", error);
       }
       else if(paramValue)
       {
           BOOL idType = [scheme.paramClass hasPrefix:@"id"];
           Class paramClass = idType ? NULL : [[self class] classFromClassName:scheme.paramClass];
   
           if (!idType && ![paramValue isKindOfClass:paramClass])
           {
               error = [NSString stringWithFormat:@"%@ expect %@", key, scheme.paramClass];
               NSLogError(@"%@", error);
           }
           else
           {
               /// 设置对应的属性
               NSString *propertyName = [[self class] propertyNameFromFromParamName:key];
               NSString *selectorName = [[self class] selectorNameFromPropertyName:propertyName];
               SEL selector = NSSelectorFromString(selectorName);
   
               if ([object respondsToSelector:selector])
               {
                   #pragma clang diagnostic push
                   #pragma clang diagnostic ignored "-Warc-performSelector-leaks"
                   [object setValue:paramValue forKey:propertyName];
                   #pragma clang diagnostic pop
               }
               else
               {
                   NSLogInfo( @"%@ miss method -%@", objectClass, selectorName );
               }
           }
       }
       else
       {
           /// ok
       }
   }];
   
   if (error)
   {
       [[self class] promptUsageForObject:object schemes:schemes];
   }
   
   return (!error);
   }
   

有了这个功能组件就能减少太多的耦合，当然组件内部还会涉及资源的重用问题、宏定义、组件粒度等，这个组件化开发也是要求平时有一定的代码质量把关，基础代码扎实，喜爱抽取重构代码的，业务熟练的想必没大问题。组件开发适用于业务复杂的工程，公司其他部门可能需要你使用你的功能模块，当然你的功能模块很优秀，也可以做成SDK开源出去，个人认为有点还是大于弊端吧，待之后该组件开发完，再继续完善。