Customizable follow.limit

[NAR8789]

Closes #188: Customizable follow.limit. Allows customization of how many entries to show for a given follow, so I can e.g. show more entries for hackernews, because that thing is a firehose.

• Kind of quirky/amusing if set to 1 or 0.
• My attempt at min validation doesn't currently work.
• Aside from that, seems to be working if I load it as an unpacked extension in chrome. Feedback welcome on whether I'm missing any important conventions?

What's the best way to test this thoroughly? My own use of Fraidycat so far is only as a browser extension, but I know it's available in a variety of forms.

Note: I'm the same person as @xiao-maven, requester of #188. I forgot to switch out of my work account earlier.

[NAR8789]

🤔 questions / todo:

• magic number 10 is kind of littered around inside view.js. Would it make sense to import that value from storage.js, or would importing from storage.js be smelly?
• might be nice to just show expanded list for follows with only one entry (get rid of the toggle arrow, and show the full top post title, using the same amount of space)
• Looks like I'm pulling a string out of that number input. Should probably clean this up. (though, funnily, currenty does the right things--works as intended in the happy case, discards empty input (defaults to 10), keeps 0 (doesn't default to 10))
• seems not to be able to show more than 20 entries at the moment. some other limit I haven't found yet here...

[paveloom]

@xiao-maven, @kickscondor, what's the current status of this feature?

Would love to see this implemented, as many of my feeds update more than 10 times within a half of a day.

[kickscondor]

I'm very sorry - I've been consumed with another project that is eating up all of my time through March.

I was previously working on #30 - which adds pagination - a much better option than these limits - which requires no configuration. Once I'm able to get back to releasing that version, I'm hoping everyone interested in this pull request will be satisfied. If not, we can revisit this pull request at that time.

Wish I had a better answer! I will get back to this!