2020-12-03 04:17:02 +01:00
|
|
|
# typed: strict
|
|
|
|
|
|
|
|
module Cask
|
|
|
|
class Cask
|
2023-07-21 11:45:34 -04:00
|
|
|
def appdir; end
|
|
|
|
|
2020-12-07 16:31:45 +01:00
|
|
|
def artifacts; end
|
|
|
|
|
2021-01-04 13:35:07 -08:00
|
|
|
def auto_updates; end
|
|
|
|
|
|
|
|
def caveats; end
|
|
|
|
|
|
|
|
def conflicts_with; end
|
|
|
|
|
|
|
|
def container; end
|
|
|
|
|
2023-07-21 11:45:34 -04:00
|
|
|
def depends_on; end
|
|
|
|
|
2021-01-04 13:35:07 -08:00
|
|
|
def desc; end
|
|
|
|
|
2023-12-17 18:07:51 -05:00
|
|
|
def discontinued?; end
|
|
|
|
|
2023-12-04 13:43:39 -05:00
|
|
|
def deprecated?; end
|
|
|
|
|
|
|
|
def deprecation_date; end
|
|
|
|
|
|
|
|
def deprecation_reason; end
|
|
|
|
|
2024-11-07 15:50:03 -05:00
|
|
|
def deprecation_replacement; end
|
|
|
|
|
2023-12-04 13:43:39 -05:00
|
|
|
def disabled?; end
|
|
|
|
|
|
|
|
def disable_date; end
|
|
|
|
|
|
|
|
def disable_reason; end
|
2021-01-04 13:35:07 -08:00
|
|
|
|
2024-11-07 15:50:03 -05:00
|
|
|
def disable_replacement; end
|
|
|
|
|
2020-12-03 04:17:02 +01:00
|
|
|
def homepage; end
|
2020-12-13 03:12:30 +01:00
|
|
|
|
2021-01-04 13:35:07 -08:00
|
|
|
def language; end
|
|
|
|
|
|
|
|
def languages; end
|
|
|
|
|
2023-07-21 11:45:34 -04:00
|
|
|
def livecheck; end
|
|
|
|
|
livecheck: clarify livecheckable language
Formulae, casks, and resources have a `#livecheckable?` method that
indicates whether they contain a `livecheck` block. This is intended
to be read as "has a livecheckable?", not "is livecheckable?" (as
livecheck can find versions for some packages/resources without a
`livecheck` block). Unfortunately, correct understanding of this
method's behavior [outside of documentation] relies on historical
knowledge that few people possess, so this is often confusing to
anyone who hasn't been working on livecheck since 2020.
In the olden days, a "livecheckable" was a Ruby file containing a
`livecheck` block (originally a hash) with a filename that
corresponded to a related formula. The `livecheck` blocks in
livecheckable files were integrated into their respective formulae in
August 2020, so [first-party] livecheckables ceased to exist at that
time. From that point forward, we simply referred to these as
`livecheck` blocks.
With that in mind, this clarifies the situation by replacing
"livecheckable" language. This includes renaming `#livecheckable?` to
`#livecheck_defined?`, replacing usage of "livecheckable" as a noun
with "`livecheck` block", replacing "livecheckable" as a boolean with
"livecheck_defined", and replacing incorrect usage of "livecheckable"
as an adjective with "checkable".
2024-11-27 18:20:56 -05:00
|
|
|
def livecheck_defined?; end
|
|
|
|
|
2023-07-21 11:45:34 -04:00
|
|
|
def livecheckable?; end
|
|
|
|
|
2021-01-04 13:35:07 -08:00
|
|
|
def name; end
|
|
|
|
|
2023-07-21 11:45:34 -04:00
|
|
|
def on_system_blocks_exist?; end
|
|
|
|
|
2024-08-23 16:39:23 +01:00
|
|
|
sig { returns(T.nilable(MacOSVersion)) }
|
|
|
|
def on_system_block_min_os; end
|
|
|
|
|
2021-01-04 13:35:07 -08:00
|
|
|
def sha256; end
|
|
|
|
|
2020-12-13 03:12:30 +01:00
|
|
|
def staged_path; end
|
2021-01-04 13:35:07 -08:00
|
|
|
|
2024-08-23 16:39:23 +01:00
|
|
|
sig { returns(T.nilable(::Cask::URL)) }
|
2021-01-04 13:35:07 -08:00
|
|
|
def url; end
|
|
|
|
|
|
|
|
def version; end
|
2020-12-03 04:17:02 +01:00
|
|
|
end
|
|
|
|
end
|