Use number for array indexes in ToPath

[NicolasCwy]

Would it be possible to add an option to make paths in array format instead of dot format
Some form item libraries e.g Antd use arrays of strings/ number to denote the path, essentially splitting them by the "." that separates them.

type Obj = {
  a: {
    b: {
      e: string;
    };
    c: {
      d: ['foo'];
    };
  };
};

// Current feature
a.c.d[0]
a.c.d.0

// New Feature - array notation
["a", "c", "d", 0] 

Upvote & Fund

• We're using Polar.sh so you can upvote and help fund this issue.
• The funding will be given to active contributors.
• Thank you in advance for helping prioritize & fund our backlog.

[NicolasCwy]

Seems like what is needed is in the Get source file, with some slight tweaks

// Current behaviour
ToPath<'foo[0].bar.baz'>
//=> ['foo', '0', 'bar', 'baz']

// Expected behaviour
ToPath<'foo[0].bar.baz'>
//=> ['foo', 0, 'bar', 'baz'] // 0 should be a number since it is an array index

[fregante]

Seems like what is needed is in the Get

Can this whole request be summarized into: Use number for array indexes in ToPath?

[NicolasCwy]

Yes and also ToPath has to be exported as well. Let me change the title and description

[voxpelli]

Question to other maintainers: At what point are the path related helpers so large and complex that they merit extraction into a standalone project that focuses on them and just them?

[fregante]

Size isn't necessarily a problem but continuous requests may be. There are 10 open issues tagged component:paths and every related file has already received a lot of tweaks.

[NicolasCwy]

Cool I'm interested in working on exposing this and implementing this