UlogsV2 Development Tasks Part II

Repository: UlogsV2

These are the rest of the tasks I picked up from @surpassinggoogle for Ulogs, and they were a bit harder. The pull request is here, and the task request is once again here.

Edit: I'm including this PR as well, with test logging removal and request loading icon addition, since it's the same task.

Adding Videos to the Banner (Task 4)

This was easier than expected though, because react has a massive base of tools to use. I used react-player (but only imported the YouTube player, since they were all from there) to embed videos into the banner. The videos are a bit sketchy looking, due to the resolution, but their appearance can easily be changed with CSS. I put them in at 100% width, so that there wouldn't be white space hanging around in the banner, and don't think it looks bad at all.

Create a Ulogs-Subtags Page (Task 6)

For this, I was to create a page for ulogs that's similar to steemit's tags page. It wasn't too hard, but was the first time I really built a react component by myself! Yay! The page looks like this:

The component wasn't really the issue to building this page, as much as the steem API was. Looking at steem's page, they use the deprecated getState('/tags')

, which isn't something to be using when it's been deprecated in favor of something else. So, I wrote a new API helper in ulogs to get the trending tags, using the tags_api, and return them to the ulog-subtags page.

The start value is weird, as it's the first tag to return in the list of trending tags, so I just went with ulogs as it's the most trending of the ulog subtags. The limit is maxed at 1000, so that's the default value (not an expensive call). Then I return to the ulog-subtags component, and filter out all the non-ulogs tags.

This logic could probably be rewritten a little bit (removing the logs after this post, didn't notice I left so many in there) for clarity and speed, but it's been pared down from a much larger function that was the first working one, down to this. Since there's a 1000 tag limit on the API call, it loops around a few times, getting more tags and adding them to the final array. Within 10 calls, you get the tags seen in the previous picture, and the next ulog-subtag shows up in the 39th call, so I left it at 10 since that isn't exactly trending, and it takes a bit for that many to load. After that, it returns the tags array to render them in the table.

That's just about it, if there's anything you notice, comment below or on Github. Cheers!

Vote For Me as Your Witness

Cheers, thanks for reading! If you like my tools and content and would like to see more, Vote for me as witness or proxy your votes and I'll pick the best witnesses for you!

My Projects

Pywit- A witness tool-kit built in Python on top of Holger80's Beempy.