You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Handle null items (e.g. mistyped or otherwise mangled ID, nuked beyond dead status, etc.)
Quick test of json.loads("null") says this should mean the item/user will satisfy is None, which is an easy sanity check to add at runtime and give a friendly error message if the object doesn't exist
Current code already does this, actually; only relevant to not-yet-handled stuff like users, which mentions the possibility of null separately
Show story submitter
Stories/links, like comments, have a by field showing who submitted them
Handle "pollopt" item type? Listed under "parts" field of a "type": "poll" item
Can't imagine people will ever link directly to a poll option, so maybe summarizing the poll options when a "poll" gets linked is better? (Lot of extra API hits, though.)
Handle/differentiate items from "ask" & "show" tabs
Also of "type": "story", but will have text instead of url and usually a category-specific prefix on the title ("Ask HN:"/"Tell HN:" for "ask" tab; "Show HN:" for "show" tab)
as of writing this, has no public activity; such users are just null in the API, making users who've never posted/commented indistinguishable from nonexistent users (which should also be handled)
<bot> [Hacker News] Comment by Ringz (2 hours, 28 minutes ago): My perfect bookmark manager is Markdownload <a href="https://github.com/deathau/markdownload">https://github.com/deathau/markdownload</a> ⏎ Just save the complete page, only selected text or only the link to a markdown file or Obsidian. With downloaded, linked or without pictures. My OS and Obsidian can search those files, they have more (automatically added) metadata. ⏎ I can even edit them […]
These are things that would be nice to support/fix before declaring the plugin "stable" and releasing it on PyPI.
setup.py
-style build/install topyproject.toml
"dead": true
in Firebase JSON"text"
may be"[dead]"
,"[flagged]"
, possibly other values—but the originaltext
is hidden if a comment isdead
null
items (e.g. mistyped or otherwise mangled ID, nuked beyonddead
status, etc.)json.loads("null")
says this should mean the item/user will satisfyis None
, which is an easy sanity check to add at runtime and give a friendly error message if the object doesn't existnull
separatelyby
field showing who submitted themtext
orurl
, but seemingly not both (like a regular "story" item)"parts"
field of a"type": "poll"
itemCan't imagine people will ever link directly to a poll option, so maybe summarizing the poll options when a "poll" gets linked is better? (Lot of extra API hits, though.)
"type": "story"
, but will havetext
instead ofurl
and usually a category-specific prefix on thetitle
("Ask HN:"/"Tell HN:" for "ask" tab; "Show HN:" for "show" tab)text
only, found under "ask" taburl
field (current state as of 88c39cb:KeyError: 'url'
)text
only), 37111256 ("story" type withtext
only)url
in story & job item types #9deleted: true
,id
,time
, andtype
fields present)about
field contains"
, so make sure to decode HTML entities in user biosnull
in the API, making users who've never posted/commented indistinguishable from nonexistent users (which should also be handled)/edit?id=NNNNNN
I'll add to this if I think of more after submitting the issue.
The text was updated successfully, but these errors were encountered: