etaoin

2018-01-31T08:55:59.000102Z

Just installed 0.2.4 and when requiring the api namespace, it throws a No Such Var str/includes? - Whats up ?

igrishaev 2018-01-31T09:03:59.000303Z

let me check, probably a macro issue

igrishaev 2018-01-31T09:05:12.000286Z

@laujensen this function is available since Clojure 1.8 https://clojuredocs.org/clojure.string/includes_q

igrishaev 2018-01-31T09:06:42.000231Z

I’ve created an issue: https://github.com/igrishaev/etaoin/issues/101

2018-01-31T09:07:30.000086Z

Which ver works with 1.7?

igrishaev 2018-01-31T09:16:24.000007Z

hm, cannot remember right now. but this str/includes? was added long ago

igrishaev 2018-01-31T09:17:09.000320Z

I mean, added into the library code.

2018-01-31T11:43:29.000495Z

Not in the 0.2.4 version

igrishaev 2018-01-31T11:43:57.000439Z

could you try 0.2.3 please?

2018-01-31T12:45:53.000367Z

Ive switched to Clojure 1.8, so maybe later

2018-01-31T12:46:10.000207Z

But @igrishaev. Ive loaded it up with the latestest chromedriver, and

2018-01-31T12:46:20.000035Z

(www/with-postmortem browser {}
                  (www/go browser “<http://www.google.com>“))

2018-01-31T12:46:35.000093Z

Generates a screenshot, but rerunning that command with another website does not generate another screenshot. How might that be?

2018-01-31T12:46:40.000363Z

s/how/why/g

2018-01-31T12:51:57.000296Z

(www/with-postmortem browser {:dir-img “/Users/lau/coding/tigerbyte/resources/screens”}
                  (www/go browser “<http://www.google.com>“)
                  (prn (www/has-text? browser “search”)))


true

2018-01-31T12:52:03.000387Z

And it does seem to load the page correctly

igrishaev 2018-01-31T13:51:38.000189Z

@laujensen the with-postmortem macros generates a screenshot only then exception occurred. In your examples, everything seems to work fine, so none of artifacts should be created. To save a screenshot, just call for (www/screenshot driver "/path/to/file")

2018-01-31T23:57:47.000420Z

Yes sorry, I found it by reading the source. Consider adding it to your readme.md