Make `entry.type` consistent arcoss various APIs

[Gozala]

Following APIs seem to return different thing for entry.type:

• ipfs.files.ls-> type: 1 (While docs say it's either 'file' | 'dir' https://github.com/ipfs/js-ipfs/blob/master/docs/core-api/FILES.md#ipfsfileslspath-options)
• ipfs.files.stat -> type: 'directory'
• ipfs.ls -> type: 'dir' (Docs don't specify but given others been document as 'directory' one would assume the same)

This can be very confusing when working with all these APIs as just like ipfs-webui does.

I would like to propose normalizing to a consistent variants for type.

[achingbrain]

Yes please, this has been on the list for ages. All type fields should be one of the UnixFS data types, my preference is for lower case, kebab-case strings, though using the enum value from the UnixFS spec would also be acceptable and strings could be a UI concern, but beware that go-IPFS uses different numbers depending on context.

See also:

• mfs file type should return same type #2948 (comment)
• docs(ipfs.files.ls): type is a number #2939
• mfs list command api return types kubo#5026

[achingbrain]

Also see ipfs/kubo#7553 for another stat command that's being added.

[achingbrain]

Closing as this issue is very stale.