Added fn to get latest chrome revision(requires fetch feature)

[initprism]

No description provided.

[mdrokz]

Hey @initprism thanks for the PR but can you explain the use of this method to fetch latest chrome revision?

[initprism]

The latest_chrome_revision function returns the latest chrome revision in the platform environment.
This can be used by modifying the revision of FecherOptions if you want to use the latest Chrome version.

let revision =  headless_chrome::browser::latest_chrome_revision()?;
let fetcher_options = headless_chrome::FetcherOptions::default()
    .with_revision(revision);

let launch_options = headless_chrome::LaunchOptionsBuilder::default()
    .fetcher_options(fetcher_options)
    .build()?;
let browser = Browser::new(launch_options)?;

IMO, I don't think it's correct to always install the latest chrome revision when enable the fetch feature.
Also, the reason this function is not included in the fetcher module is that the lib does not export fetcher to pub. This will have to be reflected later to be moved to the fetcher module or written in the appropriate method.

[masc-it]

I think this is really useful @initprism, maybe it can be re-designed in a way that extends the current .with_revision("some-version") function, rather than adding a new function, e.g. we can define a Version enum that can be passed to it:

enum Version {
    Specific(S),  // S: Into<String>
    Latest
}

.with_revision(Version::Specific("634997"))
or 
.with_revision(Version::Latest)

[mdrokz]

The latest_chrome_revision function returns the latest chrome revision in the platform environment. This can be used by modifying the revision of FecherOptions if you want to use the latest Chrome version.

let revision =  headless_chrome::browser::latest_chrome_revision()?;
let fetcher_options = headless_chrome::FetcherOptions::default()
    .with_revision(revision);

let launch_options = headless_chrome::LaunchOptionsBuilder::default()
    .fetcher_options(fetcher_options)
    .build()?;
let browser = Browser::new(launch_options)?;

IMO, I don't think it's correct to always install the latest chrome revision when enable the fetch feature. Also, the reason this function is not included in the fetcher module is that the lib does not export fetcher to pub. This will have to be reflected later to be moved to the fetcher module or written in the appropriate method.

Makes sense thanks for the explanation !

[mdrokz]

maybe it would be better to refactor this into a match statement ?

[initprism]

Refactoring to match statement looks good. And reflecting the definition suggested by @masc-it looks good.

[mdrokz]

Refactoring to match statement looks good. And reflecting the definition suggested by @masc-it looks good.

Cool i will wait for you to add these changes. Then we can merge this PR

[initprism]

I'm sorry I closed this PR by mistake. (;_;)
please check #380