Handle the case where properties in new data can be multi-level path strings

[yipingliao]

Should fix: https://github.com/casetext/cases-on-fire/issues/3465

[yipingliao]

Make a wrapper obj, which has the passed-in path as its only key, where the value is newData. Then toss it into the helper function _convertObjToLevels, which recursively makes levels for all keys (including nested ones) with path strings (i.e., strings with "/" in them).

[yipingliao]

@daguej Ping on this.

[daguej]

Do we ever see anything like:

{
  'a/b/c': 1,
  'a/b/d': 2
}

_convertObjToLevels outputs { a: { b: { d: 2 } } }

[yipingliao]

@daguej Commit pushed - data conversion function should now handle all kinds of cases where the keys inside an object are "concatenated" together at any level with "/"s.

Example input:

{
  'a/b/c': 1,
  'a/b/d': 2,
  'a/b/e/f': 3,
  'a/b/e/g': 4,
  'b': {
    'foo/bar': {
      'baz': 10
    }
  },
  's/u/n': {
    'm/o/n': {
      's': 9,
      't': 8,
      'a': 7,
      'r': 6
    }
  },
  'one/two': {
    'three/four': {
      'five': 'A'
    }
  },
  'one/two/three': {
    'four': {
      'six': 'B'
    }
  },
  'one': {
    'two/three/four/seven': {
      'eight': {
        'nine/ten': 'C',
        'eleven': {}
      }
    }
  }
}

Corresponding output:

{
  "a": {
    "b": {
      "c": 1,
      "d": 2,
      "e": {
        "f": 3,
        "g": 4
      }
    }
  },
  "b": {
    "foo": {
      "bar": {
        "baz": 10
      }
    }
  },
  "s": {
    "u": {
      "n": {
        "m": {
          "o": {
            "n": {
              "s": 9,
              "t": 8,
              "a": 7,
              "r": 6
            }
          }
        }
      }
    }
  },
  "one": {
    "two": {
      "three": {
        "four": {
          "five": "A",
          "six": "B",
          "seven": {
            "eight": {
              "nine": {
                "ten": "C"
              }
              "eleven": {}
            }
          }
        }
      }
    }
  }
}

[daguej]

Stray spaces

[yipingliao]

Fixed spaces. :)

[daguej]

Potential performance optimization: we'll end up enumerating all of the keys of the object twice -- here and at 492.

Since firebase doesn't support empty objects, can we avoid the Object.keys(currentRawObj).length altogether?

[yipingliao]

Ah, I forgot that Firebase does not support empty objects, so there is no need for this check. Will push changes shortly.

[yipingliao]

Ping on this again. :) @daguej

[daguej]

Released as v2.0.1