alfred-rs 0.7.1

Write Alfred workflows easily. https://www.alfredapp.com
Documentation
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
184
185
186
187
188
189
190
191
192
193
194
195
196
197
198
199
200
201
202
203
204
205
206
207
208
209
210
211
212
213
214
215
216
217
218
219
220
221
222
223
224
225
226
227
228
229
230
231
232
233
234
235
236
237
238
239
240
241
242
243
244
245
246
247
248
249
250
251
252
253
254
255
256
257
258
259
260
261
262
263
264
265
266
267
268
269
270
271
272
273
274
275
276
277
278
279
280
281
282
283
284
285
286
287
288
289
290
291
292
293
294
295
296
297
298
299
300
301
302
303
304
305
306
307
308
309
310
311
312
313
314
315
316
317
318
319
320
321
322
323
324
325
326
327
328
329
330
331
332
333
334
335
336
337
338
339
340
341
342
343
344
345
346
347
348
349
350
351
352
353
354
355
356
357
358
359
360
361
362
363
364
365
366
367
368
369
370
371
372
373
374
375
376
377
378
379
380
381
382
383
384
385
386
387
388
389
390
391
392
393
394
395
396
397
398
399
400
401
402
403
404
405
406
407
408
409
410
411
412
413
414
415
416
417
418
419
420
421
422
423
424
425
426
427
428
429
430
431
432
433
434
435
436
437
438
439
440
441
442
443
444
445
446
447
448
449
450
451
452
453
454
455
456
457
458
459
460
461
462
463
464
465
466
467
468
469
470
471
472
473
474
475
476
477
478
479
480
481
482
483
484
485
486
487
488
489
490
491
492
493
494
495
496
497
498
499
500
501
502
503
504
505
506
507
508
509
510
511
512
513
514
515
516
517
518
519
520
521
522
523
524
525
526
527
528
529
530
531
532
533
534
535
536
537
538
539
540
541
542
543
544
545
546
547
548
549
550
551
552
553
554
555
556
557
558
559
560
561
562
563
564
565
566
567
568
569
570
571
572
573
574
575
576
577
578
579
580
581
582
583
584
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609
610
611
612
613
614
615
616
617
618
619
620
621
622
623
624
625
626
627
628
629
630
631
632
633
634
635
636
637
638
639
640
641
642
643
644
645
646
647
648
649
650
651
652
653
654
655
656
657
658
659
660
661
662
663
664
665
666
667
668
669
670
671
672
673
674
675
676
677
678
679
680
681
682
683
684
685
686
687
688
689
690
691
692
693
694
695
696
697
698
699
700
701
702
703
704
705
706
707
708
709
710
711
712
713
714
715
716
717
718
719
720
721
722
723
724
725
726
727
728
729
730
731
732
733
734
735
736
737
738
739
740
741
742
743
744
745
746
747
748
749
750
751
752
753
754
755
756
757
758
759
760
761
762
763
764
765
766
767
//! Helper for enabling Alfred workflows to upgrade themselves periodically (Alfred 3+)
//!
//! Using this module, the workflow author can make Alfred check for latest releases
//! ([`try_update_ready()`] or [`update_ready()`]) from a remote server within adjustable intervals
//! (default is 24 hrs).
//!
//! Additionally they can ask Alfred to download the new release to its cache folder for further
//! action: [`download_latest()`].
//!
//! For convenience, an associated method [`Updater::gh()`] is available to check
//! for workflows hosted on `github.com`.
//!
//! However, it's possible to check with other servers as long as the [`Releaser`] trait is
//! implemented for the desired remote service.
//! See [`Updater::new()`] documentation if you are hosting your workflow
//! on a non `github.com` service.
//!
//! ## Notes:
//! - The `github.com` hosted repository should have release items following `github`'s process.
//! This can be done by tagging a commit and then manually building a release where you
//! attach/upload `YourWorkflow.alfredworkflow` to the release page.
//! You can easily create `YourWorkflow.alfredworkflow` file by using the [export feature] of
//! Alfred in its preferences window.
//!
//! - The tag should follow all of the [semantic versioning] rules.
//! The only exception to those rules is that you can prepend your
//! semantic version tag with ASCII letter `v`: `v0.3.1` or `0.3.1`
//!
//! # Note to workflow authors
//! - Depending on network quality, checking if an update is available may take a long time.
//! This module may spawn a worker thread so that the check does not block the main flow of your plugin.
//! However given the limitations of Alfred's plugin architecture, the worker thread cannot outlive
//! your plugin's executable. This means that you either have to wait/block for the worker thread,
//! or if it is taking longer than a desirable time, you will have to abandon it.
//! See the example for more details.
//! - Workflow authors should make sure that _released_ workflow bundles have
//! their version set in [Alfred's preferences window]. However, this module provides
//! [`set_version()`] to set the version during runtime.
//!
//! [`Releaser`]: trait.Releaser.html
//! [`Updater`]: struct.Updater.html
//! [`update_ready()`]: struct.Updater.html#method.update_ready
//! [`try_update_ready()`]: struct.Updater.html#method.try_update_ready
//! [`download_latest()`]: struct.Updater.html#method.download_latest
//! [`Updater::gh()`]: struct.Updater.html#method.gh
//! [`Updater::new()`]: struct.Updater.html#method.new
//! [semantic versioning]: https://semver.org
//! [export feature]: https://www.alfredapp.com/help/workflows/advanced/sharing-workflows/
//! [Alfred's preferences window]: https://www.alfredapp.com/help/workflows/advanced/variables/
//! [`set_version()`]: struct.Updater.html#method.set_version
//! [`set_interval()`]: struct.Updater.html#method.set_interval
//!
//! # Example
//!
//! Create an updater for a workflow hosted on `github.com/spamwax/alfred-pinboard-rs`.
//! By default, it will check for new releases every 24 hours.
//! To change the interval, use [`set_interval()`] method.
//!
//! ```rust,no_run
//! # use anyhow::Result;
//! extern crate alfred;
//!
//! // This crate
//! extern crate alfred_rs;
//!
//! use alfred::{Item, ItemBuilder, json};
//! use alfred_rs::Updater;
//!
//! # use std::io;
//! # fn produce_items_for_user_to_see<'a>() -> Vec<Item<'a>> {
//! #     Vec::new()
//! # }
//! # fn do_some_other_stuff() {}
//! // Our workflow's main 'runner' function
//! fn run<'a>() -> Result<Vec<Item<'a>>> {
//!     let updater = Updater::gh("spamwax/alfred-pinboard-rs")?;
//!
//!     // Start the process for getting latest release info
//!     updater.init().expect("cannot initialize updater");
//!
//!     // We'll do some other work that's related to our workflow:
//!     do_some_other_stuff();
//!     let mut items: Vec<Item> = produce_items_for_user_to_see();
//!
//!     // We can now check if update is ready using two methods:
//!     // 1- Block and wait until we receive results from worker thread
//!     //    It's a good practice to only wait for worker for a limited time so
//!     //    our workflow doesn't become unresponsive (not shown here)
//!     let update_status = updater.update_ready();
//!
//!     // 2- Or without blocking, check if the worker thread sent the results.
//!     //    If the worker thread is still busy, we'll get an `Err`
//!     let update_status = updater.try_update_ready();
//!
//!     if let Ok(is_ready) = update_status { // Comm. with worker was successful
//!         // Check for new update and add an item to 'items'
//!         if is_ready {
//!             let update_item = ItemBuilder::new(
//!                 "New version is available!"
//!             ).into_item();
//!             // Add a new item to previous list of Items
//!             items.push(update_item);
//!         }
//!     } else {
//!         /* worker thread wasn't successful */
//!     }
//!     Ok(items)
//! }
//!
//! fn main() {
//!     // Fetch the items and show them.
//!     if let Ok(ref items) = run() {
//!         json::write_items(io::stdout(), items);
//!     }
//! }
//! ```
//!
//! An *issue* with above example can be when user is on a poor network or server is unresponsive.
//! In this case, the above snippet will try to call server every time workflow is invoked
//! by Alfred until the operation succeeds.

use super::{anyhow, bail, chrono, env_logger, semver, serde_json, url, Result};
use crate::env;
use chrono::prelude::*;
use chrono::Duration;
use reqwest;
use semver::Version;
use std::cell::RefCell;
use std::env as StdEnv;
use std::fs::{remove_file, File};
use std::io::BufWriter;
use std::path::PathBuf;
use std::sync::mpsc::Receiver;
use url::Url;
mod imp;
mod releaser;

#[cfg(test)]
mod tests;

/// Default update check interval duration (24 hrs). To change the interval use the
/// [`set_interval()`] method.
///
/// [`set_interval()`]: struct.Updater.html#method.set_interval
pub const UPDATE_INTERVAL: i64 = 24 * 60 * 60;

pub use self::releaser::GithubReleaser;
pub use self::releaser::Releaser;

/// Struct to check for & download the latest release of workflow from a remote server.
pub struct Updater<T>
where
    T: Releaser,
{
    state: imp::UpdaterState,
    releaser: RefCell<T>,
}

impl Updater<GithubReleaser> {
    /// Create an `Updater` object that will interface with a `github` repository.
    ///
    /// The `repo_name` should be in `user_name/repository_name` form. See the
    /// [module level documentation](./index.html) for full example and description.
    ///
    /// ```rust
    /// # extern crate alfred_rs;
    /// use alfred_rs::Updater;
    ///
    /// # use std::env;
    /// # fn main() {
    /// # env::set_var("alfred_workflow_uid", "abcdef");
    /// # env::set_var("alfred_workflow_data", env::temp_dir());
    /// # env::set_var("alfred_workflow_cache", env::temp_dir());
    /// # env::set_var("alfred_workflow_version", "0.0.0");
    /// let updater = Updater::gh("spamwax/alfred-pinboard-rs").expect("cannot initiate Updater");
    /// # }
    /// ```
    ///
    /// This only creates an `Updater` without performing any network operations.
    /// To check availability of a new release, launch and check for updates by
    /// using [`init()`] and [`update_ready()`] or [`try_update_ready()`] methods.
    ///
    /// To download an available release use [`download_latest()`] method afterwards.
    ///
    /// # Errors
    /// Error will happen during calling this method if:
    /// - `Updater` state cannot be read/written during instantiation, or
    /// - The workflow version cannot be parsed as semantic version compatible identifier.
    ///
    /// [`init()`]: struct.Updater.html#method.init
    /// [`update_ready()`]: struct.Updater.html#method.update_ready
    /// [`try_update_ready()`]: struct.Updater.html#method.try_update_ready
    /// [`download_latest()`]: struct.Updater.html#method.download_latest
    pub fn gh<S>(repo_name: S) -> Result<Self>
    where
        S: Into<String>,
    {
        let releaser = GithubReleaser::new(repo_name);

        Self::load_or_new(releaser)
    }
}

impl<T> Updater<T>
where
    T: Releaser + Send + 'static,
{
    /// Create an `Updater` object that will interface with a remote repository for updating operations.
    ///
    /// `repo_name` is an arbitrary tag/identifier associated with the remote repository.
    ///
    /// How the `Updater` interacts with the remote server should be implemented using the [`Releaser`]
    /// trait. This crate provides a default implementation for interacting with
    /// `github.com` repositories, see [`gh()`] and [`GithubReleaser`].
    ///
    /// # Example
    ///
    /// ```rust,no_run
    /// # extern crate alfred_rs;
    /// # extern crate semver;
    /// # use anyhow::Result;
    /// # extern crate url;
    ///
    /// use url::Url;
    /// use semver::Version;
    ///
    /// use alfred_rs::Updater;
    /// use alfred_rs::updater::Releaser;
    /// # use std::env;
    /// # fn main() {
    ///
    /// #[derive(Clone)]
    /// struct MyPrivateHost {/* inner */};
    ///
    /// // You need to actually implement the trait, following is just a mock.
    /// impl Releaser for MyPrivateHost {
    ///     type SemVersion = Version;
    ///     type DownloadLink = Url;
    ///
    ///     fn new<S: Into<String>>(project_id: S) -> Self {
    ///         MyPrivateHost {}
    ///     }
    ///
    ///     fn fetch_latest_release(&self) -> Result<(Version, Url)> {
    ///         let version = Version::new(1, 0, 12);
    ///         let url = Url::parse("https://ci.remote.cc/release/latest")?;
    ///         Ok((version, url))
    ///     }
    /// }
    ///
    /// let updater: Updater<MyPrivateHost> =
    ///     Updater::new("my_hidden_proj").expect("cannot initiate Updater");
    /// # }
    /// ```
    ///
    /// This only creates an `Updater` without performing any network operations.
    /// To check availability of a new release, launch and check for updates by
    /// using [`init()`] and [`update_ready()`] or [`try_update_ready()`] methods.
    ///
    /// To check availability of a new release use [`update_ready()`] method.
    ///
    /// To download an available release use [`download_latest()`] method afterwards.
    ///
    /// # Errors
    /// Error will happen during calling this method if:
    /// - `Updater` state cannot be read/written during instantiation, or
    /// - The workflow version cannot be parsed as a semantic version compatible identifier.
    ///
    /// [`init()`]: struct.Updater.html#method.init
    /// [`update_ready()`]: struct.Updater.html#method.update_ready
    /// [`try_update_ready()`]: struct.Updater.html#method.try_update_ready
    /// [`download_latest()`]: struct.Updater.html#method.download_latest
    /// [`Releaser`]: trait.Releaser.html
    /// [`GithubReleaser`]: struct.GithubReleaser.html
    /// [`gh()`]: struct.Updater.html#method.gh
    pub fn new<S>(repo_name: S) -> Result<Updater<T>>
    where
        S: Into<String>,
    {
        let releaser = Releaser::new(repo_name);
        Self::load_or_new(releaser)
    }

    /// Initializes `Updater` to fetch latest release information.
    ///
    /// - If it has been more than [`UPDATE_INTERVAL`] seconds (see [`set_interval()`]) since last check,
    /// the method will spawn a worker thread.
    /// In the background, the spawned thread will attempt to make a network call to fetch metadata of releases
    /// *only if* `UPDATE_INTERVAL` seconds has passed since the last network call.
    ///
    /// - All calls, which happen before the `UPDATE_INTERVAL` seconds, will initialize the `Updater`
    /// by using a local cache to report metadata about a release.
    ///
    /// For `Updater`s talking to `github.com`, the worker thread will only fetch a small
    /// metadata information to extract the version of the latest release.
    ///
    /// To check on status of worker thread and to get latest release status, use either of
    /// [`update_ready()`] or [`try_update_ready()`] methods.
    ///
    /// # Example
    ///
    /// ```rust,no_run
    /// # extern crate alfred_rs;
    /// # use anyhow::Result;
    /// # use alfred_rs::Updater;
    /// # use std::env;
    /// # fn do_some_other_stuff() {}
    /// # fn test_async() -> Result<()> {
    /// let updater = Updater::gh("spamwax/alfred-pinboard-rs")?;
    ///
    /// let rx = updater.init().expect("Error in starting updater.");
    ///
    /// // We'll do some other work that's related to our workflow while waiting
    /// do_some_other_stuff();
    ///
    /// // We can now check if update is ready using two methods:
    /// // 1- Block and wait until we receive results or errors
    /// let update_status = updater.update_ready();
    ///
    /// // 2- Or without blocking, check if the worker thread sent the results.
    /// //    If the worker thread is still busy, we'll get an `Err`
    /// let update_status = updater.try_update_ready();
    ///
    /// if let Ok(is_ready) = update_status {
    ///     // Everything went ok:
    ///     // No error happened during operation of worker thread
    ///     // and we received release info
    ///     if is_ready {
    ///         // there is an update available.
    ///     }
    /// } else {
    ///     /* either the worker thread wasn't successful or we couldn't get its results */
    /// }
    /// # Ok(())
    /// # }
    /// # fn main() {
    /// # test_async();
    /// # }
    /// ```
    ///
    /// # Errors
    /// Followings can cause the method return an error:
    /// - A worker thread cannot be spawned
    /// - Alfred environment variable error
    /// - File IO error
    ///
    /// [`set_interval()`]: struct.Updater.html#method.set_interval
    /// [`update_ready()`]: struct.Updater.html#method.update_ready
    /// [`try_update_ready()`]: struct.Updater.html#method.try_update_ready
    /// [`UPDATE_INTERVAL`]: constant.UPDATE_INTERVAL.html
    #[allow(clippy::missing_panics_doc)]
    pub fn init(&self) -> Result<()> {
        use self::imp::LATEST_UPDATE_INFO_CACHE_FN_ASYNC;
        use std::sync::mpsc;
        let _ = env_logger::try_init();

        debug!("entering init");

        // file for status of last update check
        let p = Self::build_data_fn()?.with_file_name(LATEST_UPDATE_INFO_CACHE_FN_ASYNC);

        let (tx, rx) = mpsc::channel();

        if self.last_check().is_none() {
            self.set_last_check(Utc::now());
            self.save()?;
            // This send is always successful
            tx.send(Ok(None)).unwrap();
            debug!("  last check was set to now()");
        } else if self.due_to_check() {
            // it's time to talk to remote server
            debug!(" calling start_releaser_worker");
            self.start_releaser_worker(tx, p)?;
        } else {
            debug!("  calling read_last_check_status");
            let status = Self::read_last_check_status(&p)
                .map(|last_check| {
                    last_check.and_then(|info| {
                        debug!("  read last_check_status: {:?}", info);
                        if self.current_version() < info.version() {
                            Some(info)
                        } else {
                            None
                        }
                    })
                })
                .or(Ok(None));
            debug!("  status: {:?}", status);
            tx.send(status).unwrap();
        }
        *self.state.borrow_worker_mut() = Some(imp::MPSCState::new(rx));
        debug!("successfully set the state of release worker");
        Ok(())
    }

    /// Checks if a new update is available by waiting for the background thread to finish
    /// fetching release info (blocking).
    ///
    /// In practice, this method will block if it has been more than [`UPDATE_INTERVAL`] seconds
    /// since last check. In any other instance the updater will return the update status
    /// that was cached since last check.
    ///
    /// This method will wait for worker thread (spawned by calling [`init()`]) to deliver release
    /// information from remote server.
    /// Upon successful retrieval, this method will compare release information to the current
    /// vertion of the workflow. The remote repository should tag each release according to semantic
    /// version scheme for this to work.
    ///
    /// You should use this method after calling `init()`, preferably after your workflow is done with other tasks
    /// and now wants to get information about the latest release.
    ///
    /// # Note
    ///
    /// - Since this method may block the current thread until a response is received from remote server,
    /// workflow authors should consider scenarios where network connection is poor and the block can
    /// take a long time (>1 second), and devise their workflow around it. An alternative to
    /// this method is the non-blocking [`try_update_ready()`].
    /// - The *very first* call to this method will always return false since it is assumed that
    /// user has just downloaded and installed the workflow.
    ///
    /// # Example
    ///
    /// ```no_run
    /// # extern crate alfred_rs;
    /// # use anyhow::Result;
    /// use alfred_rs::Updater;
    ///
    /// # use std::io;
    /// # fn main() {
    /// let updater =
    ///     Updater::gh("spamwax/alfred-pinboard-rs").expect("cannot initiate Updater");
    /// updater.init().expect("cannot start the worker thread");
    ///
    /// // Perform other workflow related tasks...
    ///
    /// assert_eq!(true, updater.update_ready().expect("cannot get update information"));
    ///
    /// # }
    /// ```
    ///
    /// # Errors
    /// Error will be returned :
    /// - If worker thread has been interrupted
    /// - If [`init()`] method has not been called successfully before this method
    /// - If worker could not communicate with server
    /// - If any file error or Alfred environment variable error happens
    ///
    /// [`init()`]: struct.Updater.html#method.init
    /// [`try_update_ready()`]: struct.Updater.html#method.try_update_ready
    /// [`UPDATE_INTERVAL`]: constant.UPDATE_INTERVAL.html
    pub fn update_ready(&self) -> Result<bool> {
        if self.state.borrow_worker().is_none() {
            bail!("update_ready_sync is deprecated. use init()");
        }
        self.update_ready_async(false)
    }

    /// Try to get release info from background worker and see if a new update is available (non-blocking).
    ///
    /// This method will attempt to receive release information from worker thread
    /// (spawned by calling [`init()`]). Upon successful retrieval, this method will compare
    /// release information to the current vertion of the workflow.
    /// The remote repository should tag each release according to semantic version scheme
    /// for this to work.
    ///
    /// If communication with worker thread is not successful or if the worker thread could not
    /// fetch release information, this method will return an error.
    ///
    /// You should use this method after calling `init()`, preferably after your workflow is done with other tasks
    /// and now wants to get information about the latest release.
    ///
    /// # Note
    ///
    /// - To wait for the worker thread to deliver its release information you can use the blocking
    /// [`update_ready()`] method.
    /// - The *very first* call to this method will always return false since it is assumed that
    /// user has just downloaded and installed the workflow.
    ///
    /// # Example
    ///
    /// ```no_run
    /// extern crate alfred_rs;
    /// # use anyhow::Result;
    ///
    /// use alfred_rs::Updater;
    ///
    /// # use std::io;
    ///
    /// # fn do_some_other_stuff() {}
    ///
    /// fn main() {
    /// let updater =
    ///     Updater::gh("spamwax/alfred-pinboard-rs").expect("cannot initiate Updater");
    /// updater.init().expect("cannot start the worker thread");
    ///
    /// // Perform other workflow related tasks...
    /// do_some_other_stuff();
    ///
    /// assert_eq!(true, updater.try_update_ready().expect("cannot get update information"));
    ///
    /// // Execution of program will immediately follow to here since this method is non-blocking.
    ///
    /// }
    /// ```
    ///
    /// # Errors
    /// Error will be returned :
    /// - If worker thread is not ready to send information or it has been interrupted
    /// - If [`init()`] method has not been called successfully before this method
    /// - If worker could not communicate with server
    /// - If any file error or Alfred environment variable error happens
    ///
    /// [`init()`]: struct.Updater.html#method.init
    /// [`update_ready()`]: struct.Updater.html#method.update_ready
    pub fn try_update_ready(&self) -> Result<bool> {
        if self.state.borrow_worker().is_none() {
            bail!("update_ready_sync is deprecated. use init()");
        }
        self.update_ready_async(true)
    }

    /// Set workflow's version to `version`.
    ///
    /// Content of `version` needs to follow semantic versioning.
    ///
    /// This method is provided so workflow authors can set the version from within the Rust code.
    ///
    /// # Example
    ///
    /// ```rust
    /// # extern crate alfred_rs;
    /// # use anyhow::Result;
    /// # use alfred_rs::Updater;
    /// # use std::env;
    /// # fn ex_set_version() -> Result<()> {
    /// # env::set_var("alfred_workflow_uid", "abcdef");
    /// # env::set_var("alfred_workflow_data", env::temp_dir());
    /// # env::set_var("alfred_workflow_version", "0.0.0");
    /// let mut updater = Updater::gh("spamwax/alfred-pinboard-rs")?;
    /// updater.set_version("0.23.3");
    /// # Ok(())
    /// # }
    ///
    /// # fn main() {
    /// #     ex_set_version();
    /// # }
    /// ```
    /// An alternative (recommended) way of setting version is through [Alfred's preferences window].
    ///
    /// [Alfred's preferences window]: https://www.alfredapp.com/help/workflows/advanced/variables/
    ///
    /// # Panics
    /// The method will panic if the passed value `version` cannot be parsed as a semantic version compatible string.
    pub fn set_version<S: AsRef<str>>(&mut self, version: S) {
        let v = Version::parse(version.as_ref())
            .expect("version should follow semantic version rules.");
        self.state.set_version(v);

        StdEnv::set_var("alfred_workflow_version", version.as_ref());
    }

    /// Set the interval between checks for a newer release (in seconds)
    ///
    /// [Default value][`UPDATE_INTERVAL`] is 86,400 seconds (24 hrs).
    ///
    /// # Example
    /// Set interval to be 7 days
    ///
    /// ```rust
    /// # extern crate alfred_rs;
    /// # use alfred_rs::Updater;
    /// # use std::env;
    /// # fn main() {
    /// # env::set_var("alfred_workflow_uid", "abcdef");
    /// # env::set_var("alfred_workflow_data", env::temp_dir());
    /// # env::set_var("alfred_workflow_cache", env::temp_dir());
    /// # env::set_var("alfred_workflow_version", "0.0.0");
    /// let mut updater =
    ///     Updater::gh("spamwax/alfred-pinboard-rs").expect("cannot initiate Updater");
    /// updater.set_interval(7 * 24 * 60 * 60);
    /// # }
    /// ```
    /// [`UPDATE_INTERVAL`]: constant.UPDATE_INTERVAL.html
    pub fn set_interval(&mut self, tick: i64) {
        self.set_update_interval(tick);
    }

    /// Check if it is time to ask remote server for latest updates.
    ///
    /// It returns `true` if it has been more than [`UPDATE_INTERVAL`] seconds since we last
    /// checked with server (i.e. ran [`update_ready()`]), otherwise returns false.
    ///
    /// [`update_ready()`]: struct.Updater.html#method.update_ready
    ///
    /// # Example
    ///
    /// ```rust,no_run
    /// # extern crate alfred_rs;
    /// # use anyhow::Result;
    /// # use alfred_rs::Updater;
    /// # fn run() -> Result<()> {
    /// let mut updater = Updater::gh("spamwax/alfred-pinboard-rs")?;
    ///
    /// // Assuming it is has been UPDATE_INTERVAL seconds since last time we ran the
    /// // `update_ready()` and there actually exists a new release:
    /// assert_eq!(true, updater.due_to_check());
    /// # Ok(())
    /// # }
    /// # fn main() {
    /// # run();
    /// # }
    /// ```
    ///
    /// [`UPDATE_INTERVAL`]: constant.UPDATE_INTERVAL.html
    pub fn due_to_check(&self) -> bool {
        self.last_check().map_or(true, |dt| {
            debug!("last check: {}", dt);
            Utc::now().signed_duration_since(dt) > Duration::seconds(self.update_interval())
        })
    }

    /// Method to download and save the latest release into workflow's cache dir.
    ///
    /// If the download and save operations are both successful, it returns name of file in which the
    /// downloaded Alfred workflow bundle is saved.
    ///
    /// The downloaded workflow will be saved in dedicated cache folder of the workflow, and it
    /// will be always renamed to `latest_release_WORKFLOW-NAME.alfredworkflow`
    ///
    /// To install the downloaded release, your workflow needs to somehow open the saved file.
    ///
    /// Within shell, it can be installed by issuing something like:
    /// ```bash
    /// open -b com.runningwithcrayons.Alfred latest_release_WORKFLOW-NAME.alfredworkflow
    /// ```
    ///
    /// Or you can add "Run script" object to your workflow and use environment variables set by
    /// Alfred to automatically open the downloaded release:
    /// ```bash
    /// open -b com.runningwithcrayons.Alfred "$alfred_workflow_cache/latest_release_$alfred_workflow_name.alfredworkflow"
    /// ```
    ///
    /// # Note
    ///
    /// The method may take longer than other Alfred-based actions to complete. Workflow authors using this crate
    /// should implement strategies to prevent unpleasant long blocks of user's typical work flow.
    ///
    /// One option to initiate the download and upgrade process is to invoke your executable with a
    /// different argument. The following snippet can be tied to a dedicated Alfred **Hotkey**
    /// or **Script Filter** so that it is only executed when user explicitly asks for it:
    ///
    /// # Example
    ///
    /// ```rust,no_run
    /// # extern crate alfred;
    /// # extern crate alfred_rs;
    /// # use anyhow::Result;
    /// # use std::io;
    /// use alfred_rs::Updater;
    /// use alfred::{ItemBuilder, json};
    ///
    /// # fn main() {
    /// # let updater =
    /// #    Updater::gh("spamwax/alfred-pinboard-rs").expect("cannot initiate Updater");
    /// # let cmd_line_download_flag = true;
    /// if cmd_line_download_flag && updater.update_ready().unwrap() {
    ///     match updater.download_latest() {
    ///         Ok(downloaded_fn) => {
    ///             json::write_items(io::stdout(), &[
    ///                 ItemBuilder::new("New version of workflow is available!")
    ///                              .subtitle("Click to upgrade!")
    ///                              .arg(downloaded_fn.to_str().unwrap())
    ///                              .variable("update_ready", "yes")
    ///                              .valid(true)
    ///                              .into_item()
    ///             ]);
    ///         },
    ///         Err(e) => {
    ///             // Show an error message to user or log it.
    ///         }
    ///     }
    /// }
    /// #    else {
    /// #    }
    /// # }
    /// ```
    ///
    /// For the above example to automatically work, you then need to connect the output of the script
    /// to an **Open File** action so that Alfred can install/upgrade the new version.
    ///
    /// As suggested in above example, you can add an Alfred variable to the item so that your workflow
    /// can use it for further processing.
    ///
    /// # Errors
    /// Downloading latest workflow can fail if network error, file error or Alfred environment variable
    /// errors happen, or if [`Releaser`] cannot produce a usable download url.
    ///
    /// [`Releaser`]: trait.Releaser.html
    pub fn download_latest(&self) -> Result<PathBuf> {
        let url = self
            .state
            .download_url()
            .ok_or_else(|| anyhow!("no release info avail yet"))?;
        let client = reqwest::blocking::Client::new();

        client
            .get(url)
            .send()?
            .error_for_status()
            .map_err(Into::into)
            .and_then(|mut resp| {
                // Get workflow's dedicated cache folder & build a filename
                let workflow_name = env::workflow_name()
                    .unwrap_or_else(|| "WhyUNoNameYourOwnWorkflow".to_string())
                    .chars()
                    .map(|c| if c.is_ascii_alphanumeric() { c } else { '_' })
                    .collect::<String>();
                let latest_release_downloaded_fn = env::workflow_cache()
                    .ok_or_else(|| {
                        anyhow!(
                            "missing env variable for cache dir. forgot to set workflow bundle id?",
                        )
                    })
                    .map(|mut cache_dir| {
                        cache_dir
                            .push(["latest_release_", &workflow_name, ".alfredworkflow"].concat());
                        cache_dir
                    })?;
                // Save the file
                File::create(&latest_release_downloaded_fn)
                    .map_err(Into::into)
                    .and_then(|fp| {
                        let mut buf_writer = BufWriter::with_capacity(0x10_0000, fp);
                        resp.copy_to(&mut buf_writer)?;
                        Ok(())
                    })
                    .map_err(|e: anyhow::Error| {
                        let _r = remove_file(&latest_release_downloaded_fn);
                        e
                    })?;
                Ok(latest_release_downloaded_fn)
            })
    }

    /// Returns the version for the latest downloadable workflow from [`Releaser`].
    /// `None` is returned if no release info has yet been fetched from server.
    ///
    /// # Note
    /// This method does not perform any network or disk IO. It merely returns the cached
    /// version info based on last successful communication with the remote server.
    /// So it is possible the method will return a version different than server's version if:
    /// - It's been less than [`UPDATE_INTERVAL`] seconds since last check, or
    /// - Worker thread is busy checking and you called this method before it finishes.
    ///
    /// [`Releaser`]: trait.Releaser.html
    /// [`UPDATE_INTERVAL`]: constant.UPDATE_INTERVAL.html
    /// [`update_ready()`]: struct.Updater.html#method.update_ready
    /// [`try_update_ready()`]: struct.Updater.html#method.try_update_ready
    pub fn latest_avail_version(&self) -> Option<Version> {
        self.state.latest_avail_version()
    }

    /// Get workflow's current version
    pub fn current_version(&self) -> &Version {
        self.state.current_version()
    }
}