fix issue getting number value for oneof field

[pyu10055]

There was a bug with operations that use integer parameters such as Split. These were being given a default float value of 0, so param.f was never evaluating to undefined. Accordingly, the result for all integer parameters was always 0.

Fixes 535

---

This change is 

[dsmilkov]

Nice catch! Requesting a few more unit tests to make sure I got 'bool' and 'float' covered as well.

Reviewed 2 of 2 files at r1.
Reviewable status: 0 of 1 approvals obtained (waiting on @pyu10055 and @dsmilkov)

---

src/operations/operation_mapper_test.ts, line 105 at r1 (raw file):

      attr: {squeeze_dims: {list: {i: [Long.fromInt(1), Long.fromInt(2)]}}}
    },
    {

Can you add a few more unit tests for ops that have

1. float param, (with and without default value), such as FusedBatchNorm which has:

attr {
    name: "epsilon"
    type: "float"
    default_value {
      f: 0.0001
    }
  } 

2. bool param (again with and without default value), such as FusedBatchNorm which as:

attr {
    name: "is_training"
    type: "bool"
    default_value {
      b: true
    }
  }

[pyu10055]

Reviewable status: 0 of 1 approvals obtained (waiting on @pyu10055)

---

src/operations/operation_mapper_test.ts, line 105 at r1 (raw file):

Previously, dsmilkov (Daniel Smilkov) wrote…

Can you add a few more unit tests for ops that have

1. float param, (with and without default value), such as FusedBatchNorm which has:

attr {
    name: "epsilon"
    type: "float"
    default_value {
      f: 0.0001
    }
  } 

2. bool param (again with and without default value), such as FusedBatchNorm which as:

attr {
    name: "is_training"
    type: "bool"
    default_value {
      b: true
    }
  }

added float value, there is already a bool value test.