Fork me on GitHub
#perun
<
2017-03-15
>
bhagany10:03:37

@podviaznikov are you working on the new feature requests you submitted last night? If you are not, your timing is perfect :)

bhagany10:03:58

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!

bhagany17:03:45

by the way, if anyone has any other feature requests, now's the time 🙂

martinklepsch17:03:53

I only have boring ideas: docstrings + validation of return values of user supplied functions

podviaznikov18:03:47

@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

bhagany18:03:11

perfect timing

podviaznikov18:03:57

Perfect indeed:)

podviaznikov18:03:57

let me know if you need more details. I wasn’t very verbose in the description

bhagany18:03:19

I think I understand, but I'll be doing some prep this afternoon. If I have questions, you'll be sure to know 🙂

bhagany22:03:36

@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?

bhagany22:03:16

(I have a manifest.json on my site too, and that's all I intend it for)

podviaznikov22:03:48

I was thinking about just “installing”

podviaznikov22:03:01

basically straight from the HTML spec

bhagany22:03:44

okay, I think that's the same thing

bhagany23:03:32

@podviaznikov have you thought about how to handle cache invalidations, re: #180?

podviaznikov23:03:55

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

podviaznikov23:03:01

if you have some other ideas, definitely share them