Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
  • Dec 01 22:32
    GitLab | Robbie Antenesse pushed 4 commits to Readlebee
  • Dec 01 01:03
    GitLab | Robbie Antenesse pushed 2 commits to Readlebee
  • Oct 28 06:02
    GitLab | Robbie Antenesse pushed 4 commits to Readlebee
  • Oct 26 18:21
    GitLab | Robbie Antenesse pushed 3 commits to Readlebee
  • Oct 19 22:35
    GitLab | Robbie Antenesse pushed 6 commits to Readlebee
  • Oct 08 18:41
    GitLab | Robbie Antenesse pushed 13 commits to Readlebee
  • Oct 08 18:38
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Oct 06 23:59
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Oct 03 19:13
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Sep 28 00:40
    GitLab | Robbie Antenesse pushed 6 commits to Readlebee
  • Sep 27 02:03
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Sep 27 00:58
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Sep 27 00:55
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Sep 27 00:48
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Sep 27 00:39
    GitLab | Robbie Antenesse pushed 1 commits to Readlebee
  • Sep 26 20:02
    GitLab | Robbie Antenesse pushed to Readlebee
  • Sep 26 19:59
    GitLab | Robbie Antenesse pushed 3 commits to Readlebee
  • Sep 26 19:05
    GitLab | Robbie Antenesse pushed to Readlebee
  • Sep 26 19:04
    GitLab | Robbie Antenesse pushed 16 commits to Readlebee
  • Sep 26 19:04
    GitLab | Robbie Antenesse pushed 8 commits to Readlebee
Robbie Antenesse
@Alamantus
So I'm working on the search styling right now, and I'm coming up against a little bit of a problem—Inventaire delivers cover art separately from the book data, which means it takes a separate API call to get it. The regular search from Inventaire is already pretty slow, so I don't want to slow it down even more by doing all the essential API calls at once for every search result.
So to solve the problem, I'm going to return just the search results with the name and only try to load the covers after the user clicks the interaction buttons. It'll open a modal window that shows a quick view of Readlebee data like average rating, number of shelves it's on, and a few of the most-liked reviews, plus a link to the book page that will load all the reviews and details about it and a link to the Inventaire page to display information about the actual book.
Robbie Antenesse
@Alamantus
I'll have to make sure the messaging is very clear and have the reason for the split written very clearly somewhere (maybe at account creation) so it's not too confusing for users.
Robbie Antenesse
@Alamantus
I find it very strange that the import process in Inventaire creates duplicate records for some books and authors but is able to find the correct records for others when the name for either is exactly identical to the existing ones...
For example, parts 1–3 of Warbreaker by Brandon Sanderson produced 2 correct author connections with the existing Brandon Sanderson record and 1 duplicate... and this was in the same import batch. I have no clue why this could happen, and I can't find the import code on their GitHub repo yet.
Robbie Antenesse
@Alamantus
I'm planning on starting a11y testing early in development, and I'm kind of stuck between just using pa11y (or its GUI alter ego koa11y) and using aXe, which I think I just got beta access to?
The big draw to aXe is its straightforward approach and simple English phrasing of tests, but it feels like it has a lot of moving parts and might actually require Google Chrome, which I'm not a huge fan of.
Pa11y, on the other hand, can be used anywhere and seems to do the trick just as easily (and even easier if you use Koa11y!), which is a huge draw to me.
I'll probably try both out, but I expect I'll end up with pa11y because of its cross-platform nature.
No matter what I use, the earlier I integrate accessibility tests and stuff into Readlebee, the easier it will be to write the code with it in mind rather than needing to go back and add it all later!