小编Gau*_*jan的帖子

我们都知道这constructor -> componentWillMount -> componentDidMount是执行的顺序.

现在,当redux发挥作用并尝试在组件生命周期中访问redux属性时.什么是该命令连接将执行,这样数据可用的生命周期方法忽略和数据更新用,以终极版.可能性是

1. Connect (DATA AVAILABLE) -> constructor & componentWillMount & componentDidMount

2. constructor -> Connect (DATA AVAILABLE) -> componentWillMount & componentDidMount

3. constructor -> componentWillMount -> Connect (DATA AVAILABLE) -> componentDidMount

4. constructor -> componentWillMount -> componentDidMount -> Connect (DATA AVAILABLE) 

并且订单是否一致或取决于加载的数据？

反应和原生反应是不同的

并且可以根据PropType中的要求定义redux属性

通过将mathjax cdn链接为react native来使用webview呈现数学内容是很常见的。但是如何解决使其脱机的问题。

1. 有没有办法在本地维护该捆绑包？

2. 甚至喜欢吗？

3. 捆绑包的大小是多少？我不希望我的应用程序大小超过10mb。

嗨，当我尝试继续出错以插入许多它在 mongoid 中不起作用时。

我设置了以下唯一索引

db.push_notifications.createIndex({ actor_vid: 1,campaign_id: 1 },{ unique: true, partialFilterExpression: { campaign_id: { $exists: true } } })

PushNotification.collection.insert_many([{:campaign_id => "1",:actor_vid => 9},{:campaign_id => "1",:actor_vid => 8}],:continue_on_error => true,:safe =>错误的）

PushNotification.collection.insert_many([{:campaign_id => "1",:actor_vid => 9},{:campaign_id => "1",:actor_vid => 10}],:continue_on_error => true,:safe =>假）抛出

Mongo::Error::BulkWriteError: Mongo::Error::BulkWriteError 来自 /home/deploy/.bundler/notification_service/ruby/2.2.0/gems/mongo-2.2.5/lib/mongo/bulk_write/result.rb： 184:in validate!' from /home/deploy/.bundler/notification_service/ruby/2.2.0/gems/mongo-2.2.5/lib/mongo/bulk_write/result_combiner.rb:73:inresult' from /home/deploy/.bundler/notification_service/ruby/2.2.0/gems/mongo-2.2.5/lib/mongo/bulk_write.rb:65:in execute' from /home/deploy/.bundler/notification_service/ruby/2.2.0/gems/mongo-2.2.5/lib/mongo/collection.rb:385:inbulk_write' from /home/deploy/。 bundler/notification_service/ruby/2.2.0/gems/mongo-2.2.5/lib/mongo/collection.rb:363:in insert_many' from /home/deploy/.bundler/notification_service/ruby/2.2.0/gems/mongoid-5.1.3/lib/mongoid/query_cache.rb:168:ininsert_many_with_clear_cache' from (irb):133 from /home/deploy/.bundler/notification_service/ruby/ 2.2.0/gems/railties-4.2.6/lib/rails/commands/console.rb:110:in start' from /home/deploy/.bundler/notification_service/ruby/2.2.0/gems/railties-4.2.6/lib/rails/commands/console.rb:9:instart' from /home/deploy/.bundler/notification_service/ruby/2.2.0/gems/railties-4.2。 6/lib/rails/commands/commands_tasks.rb:68:inconsole' from …