Category
Version
1.0.2
Can we make it so that the properties surfaced through the search results are returned as enumerable (see: https://github.com/pnp/pnp/blob/dev/packages/sp/src/search.ts#L372, currently set to false)? I'm trying to pass through my search results object to a React component using a spread operator, but because they are not enumerable they do not get passed through. It's a bit of a pain, because it means I either need to change the way data is passed through my React/Redux flow, or craft a copy of the results object myself before passing it through.
Is there value in setting them to non-enumerable that I am missing?
Category
Version
1.0.2
Can we make it so that the properties surfaced through the search results are returned as enumerable (see: https://github.com/pnp/pnp/blob/dev/packages/sp/src/search.ts#L372, currently set to false)? I'm trying to pass through my search results object to a React component using a spread operator, but because they are not enumerable they do not get passed through. It's a bit of a pain, because it means I either need to change the way data is passed through my React/Redux flow, or craft a copy of the results object myself before passing it through.
Is there value in setting them to non-enumerable that I am missing?