This website requires JavaScript.
Explore
Help
Sign In
commons_go
/
chromedp
Watch
3
Star
0
Fork
0
You've already forked chromedp
Code
Issues
Pull Requests
Packages
Projects
Releases
Wiki
Activity
da4ac414ed
chromedp
/
.travis.yml
8 lines
47 B
YAML
Raw
Normal View
History
Unescape
Escape
Initial commit of pool and unit tests
2017-02-09 15:01:40 +00:00
language
:
go
start the chromedp v2 refactor First, we want all of the functionality in a single package; this means collapsing whatever is useful into the root chromedp package. The runner package is being replaced by the Allocator interface, with a default implementation which starts browser processes. The client package doesn't really have a place in the new design. The context, allocator, and browser types will handle the connection with each browser. Finally, the new API is context-based, hence the addition of context.go. The tests have been modified to build and run against the new API.
2019-03-05 13:14:50 +00:00
Initial commit of pool and unit tests
2017-02-09 15:01:40 +00:00
go
:
start the chromedp v2 refactor First, we want all of the functionality in a single package; this means collapsing whatever is useful into the root chromedp package. The runner package is being replaced by the Allocator interface, with a default implementation which starts browser processes. The client package doesn't really have a place in the new design. The context, allocator, and browser types will handle the connection with each browser. Finally, the new API is context-based, hence the addition of context.go. The tests have been modified to build and run against the new API.
2019-03-05 13:14:50 +00:00
-
1.12
.x
Fixing travis again
2017-02-09 15:27:15 +00:00
script
:
start the chromedp v2 refactor First, we want all of the functionality in a single package; this means collapsing whatever is useful into the root chromedp package. The runner package is being replaced by the Allocator interface, with a default implementation which starts browser processes. The client package doesn't really have a place in the new design. The context, allocator, and browser types will handle the connection with each browser. Finally, the new API is context-based, hence the addition of context.go. The tests have been modified to build and run against the new API.
2019-03-05 13:14:50 +00:00
-
true
Reference in New Issue
Copy Permalink