So, this post is going to be shorter today. I wanted to get the fifth relationship finished, but due to time constraints imposed by my upcoming flight for work, I wasn't able to quite get where I wanted. It turns out that even working on software with no attached expectations, you'll still fail to meet deadlines.
So, last time we discovered that the weight field in each vote showed the proportional contribution to the piece of content in question. Using this information, we simply need to find the vote corresponding with the author and then keep track of which post has the highest contribution. Putting that into Ruby, it looks something like this:
However, when we run all five of our relationships, we get this:
Not exactly the five different results that we wanted. Now granted, it is possible for relationships to return nil if a relevant piece of content is not found. But to make things worse, another issue arises when we see that a comment shows up as one of the results. Which means that there is a filtering issue somewhere.
Well that does it for today. Since I'll be away for work, we'll be taking a week hiatus and then begin cleaning stuff up and fixing some problems areas in the next several posts.
This post has been just added as new item to timeline of Q-Filter on Steem Projects.
If you want to be notified about new updates from this project, register on Steem Projects and add Q-Filter to your favorite projects.