strange [] -> . conversion

[rodneyrehm]

Hey there,

is there a particular reason for using nested .replace() calls instead of using the capture group directly?

const text = 'due.b[0][0][0]';

const original = text.replace(/(\[.*\])/g, (str) => {
  return str
    .replace(/\[/g, '.')
    .replace(/\]/g, '');
});

const optimized = text.replace(/\[([^\]]+)\]/g, (match, token) => '.' + token);

console.log(text);
console.log(original);
console.log(optimized);

[zewish]

You could try to run the unit tests - one of the cases breaks here. I'm quite sure with some work it could be optimized though.

[rodneyrehm]

I see. This is happenning because you seem to allow nesting [due][a[0]]. In that case you can still remove the outer replacement and go with

path
  .replace(/\[/g, '.')
  .replace(/\]/g, '')
  .replace(/^\./, '')
  .split('.')

Anyway, my question "if there was a reason to…" is answered :)

[zewish]

Thanks, for that one - will do a new build with a mention to you github alias :)