Duration normalize is buggy

Duration.fromObject({ minutes: 120 }).normalize().toObject();
// => { minutes: 120 }

Does not change anything, however when I put in hours: 0 then I get

Duration.fromObject({ hours: 0, minutes: 120 }).normalize().toObject();
// => { hours: 2, minutes: 0 };

Looking at this function from the luxon code seems to reveal the issue

function normalizeValues(matrix, vals) {
  reverseUnits.reduce(function (previous, current) {
    if (!isUndefined(vals[current])) {
      if (previous) {
        convert(matrix, vals, previous, vals, current);
      }

      return current;
    } else {
      return previous;
    }
  }, null);
}

[icambron]

I’m not sure about the analogy, but yes, Luxon’s durations are just like that. It seemed too confusing for Luxon to add new keys without you telling it to (e.g. via shiftTo). You can of course add all the keys and later filter out the zeros.

[icambron]

@atruskie that’s a different problem. I think you mean example.as("years"). get is just a getter for the unit