Array-like fields in Single Pages are not returned in DataArrays

[tzhouhc]

An example:
if I have Note A as

# Note A
director:: wong kar-wai

then in a separate note, if I have an outlink to Note A, and then do dv.page or dv.current(), then the .file.outlinks accessor returns an Array, not a DataArray.

dv.paragraph(
  dv.page("Test/Note B").file.outlinks.map(p => dv.page(p.path)).director
)

The above call will return a -.

Whereas if I did dv.pages with explicit file name, I get a DataArray instead.

dv.paragraph(
  dv.pages('"Test/Note B"').file.outlinks.map(p => dv.page(p.path)).director
)

This then produces wong kar-wai as expected. Same phenomenon can be observed via .tags too, and I assume this is because when dv.page or dv.current is used, the result is a Page and not a DataArray of Pages, and thus all array-like fields are just returned as arrays.

Considering how DataArrays is already blurring the line between singletons and arrays by allowing direct dot access to member fields, is it a potential possibility to make dv.page and dv.current return DataArray instances too?

[blacksmithgu]

The reason for this discrepancy is due to some technicalities on how DataArray is implemented - it has additional settings metadata which is not known when the page metadata is initially created (but is known when it is later passed up to the API to be given to your script).

That being said, we can work around this by doing a post-processing step to convert arrays to data arrays. This also opens up some cool functionality like proxying Links to be able to directly index into them.

I'm going to convert this to an issue.