@podviaznikov are you working on the new feature requests you submitted last night? If you are not, your timing is perfect :)
I have a pair-programming job interview tomorrow. I am supposed to pick a project to work on for the interview, and obviously Perun is at the top of my list. Implementing those two features would do nicely!
by the way, if anyone has any other feature requests, now's the time 🙂
I only have boring ideas: docstrings + validation of return values of user supplied functions
@bhagany no, not working. That is the reason I submitted them in case someone would like to do them before me. So you are welcome to tackle those tasks
great!
perfect timing
Perfect indeed:)
let me know if you need more details. I wasn’t very verbose in the description
I think I understand, but I'll be doing some prep this afternoon. If I have questions, you'll be sure to know 🙂
@podviaznikov okay, here's a question for you - is your purpose for the manifest.json file solely for "installing" the site on a phone? or do you want to support other web extension features?
(I have a manifest.json on my site too, and that's all I intend it for)
I was thinking about just “installing”
basically straight from the HTML spec
okay, I think that's the same thing
... maybe
@podviaznikov have you thought about how to handle cache invalidations, re: #180?
The idea I had personally was to pass build date as cache version. So every time site is build new cache version would be generated. But it’s definitely can be smarter. I would also look how other people do it (like gatsbyjs). So it’s open investigation task
if you have some other ideas, definitely share them