You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@weex.apache.org by bb-coder <gi...@git.apache.org> on 2017/08/03 10:02:42 UTC

[GitHub] incubator-weex pull request #566: BOOL������32���������encode���'c',���� 32�...

GitHub user bb-coder opened a pull request:

    https://github.com/apache/incubator-weex/pull/566

    BOOL值在32位手机encode为'c',补充32位手机BOOL处理拆箱逻辑。

    BOOL值在32位手机encode为'c',补充32位手机BOOL处理拆箱逻辑。如果不处理，在32位上传递BOOL值将会有类型问题导致BOOL值
    不准。

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/bb-coder/incubator-weex master

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/incubator-weex/pull/566.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #566
    
----
commit 3e0e1c6ffc31a1d6b4354963c43fe6142daeb397
Author: hongbo.bhb <ho...@alibaba-inc.com>
Date:   2017-08-03T10:02:20Z

    BOOL值在32位手机encode为'c',补充32位手机BOOL处理拆箱逻辑。
    
    BOOL值在32位手机encode为'c',补充32位手机BOOL处理拆箱逻辑。如果不处理，在32位上传递BOOL值将会有类型问题导致BOOL值
    不准。

----


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-weex issue #566: BOOL������32���������encode���'c',���� 32��������...

Posted by bb-coder <gi...@git.apache.org>.
Github user bb-coder commented on the issue:

    https://github.com/apache/incubator-weex/pull/566
  
    @notdanger


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-weex issue #566: BOOL������32���������encode���'c',���� 32��������...

Posted by weex-bot <gi...@git.apache.org>.
Github user weex-bot commented on the issue:

    https://github.com/apache/incubator-weex/pull/566
  
    
    <!--
      1 failure:  This PR modify SD...
      2 warning:  No Changelog chan..., This PR should up...
      
      
    -->
    
    <table>
      <thead>
        <tr>
          <th width="50"></th>
          <th width="100%" data-danger-table="true">Fails</th>
        </tr>
      </thead>
      <tbody><tr>
          <td>:no_entry_sign:</td>
          <td>This PR modify SDK code. Please add/modify corresponding testcases. If it is ok, please comment about it. Or put '@notdanger' in you commit message.</td>
        </tr>
      </tbody>
    </table>
    
    
    <table>
      <thead>
        <tr>
          <th width="50"></th>
          <th width="100%" data-danger-table="true">Warnings</th>
        </tr>
      </thead>
      <tbody><tr>
          <td>:warning:</td>
          <td>No Changelog changes!</td>
        </tr>
      
    <tr>
          <td>:warning:</td>
          <td>This PR should update related documents as well. </td>
        </tr>
      </tbody>
    </table>
    
    
    
    <p align="right">
      Generated by :no_entry_sign: <a href="http://github.com/danger/danger-js/">dangerJS</a>
    </p>



---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---

[GitHub] incubator-weex pull request #566: BOOL������32���������encode���'c',���� 32�...

Posted by bb-coder <gi...@git.apache.org>.
Github user bb-coder closed the pull request at:

    https://github.com/apache/incubator-weex/pull/566


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastructure@apache.org or file a JIRA ticket
with INFRA.
---