Darrell Warde

Hey @AccsoSG, thanks for raising! Although in slightly different contexts, we already have this tracked in #142 and #353, but the principle remains the same. > **Further considerations:** > It...

And I just realise that my suggestion above was not all that great, as the fulltext score needs to be associated with each individual result and not the entire response!...

Hey @litewarp, apologies, I think I glossed over your suggestion! This is a super interesting idea, and I feel an appropriate use of the `edge` field!

@pandemosth, basically the "attempted workaround" in the original issue here. You need to `collect()` the results before returning them. The "fix" for this is more of a feature, hence why...

A lot of this is conceptually what we expect from Cypher results - if a GraphQL field is returned as a list, then we expect a list to be returned...

Just modified this PR to also create cards in Trello for new feature requests, which closes one of the loops of us successfully managing a backlog and roadmap.

> What about just adding the score returned from db.index.fulltext to the returned node in some way? Access to the score value would enable any user defined logic to be...

Let's not commit to this right now - let's add it to the Pagination and Sorting milestone so that we take this possibility into account whilst planning that work.

We love this idea and it's been on our minds for a long time! If we were to implement this in the library, I think constraints applied at the GraphQL...

There's some good ideas here for an eventual solution, but going to close this in favour of #138 which has been around for (a lot) longer and really the principal...