Closed kennethormandy closed 1 year ago
Added the other two workarounds I’m using here for completeness. Not necessarily expecting these are the right values to return, but they make the local development environment usable.
@kennethormandy I think the assetrev-style "return the path on failure" is a little awkward, so I just made sure the URL helpers return null
, so you can do a quick ternary in your templates.
Did you have a use-case for calling getBucketName
?
Currently, you get an error if you try and use
artifactUrl()
without manually checking theisCraftCloud
variable yourself. In practice, I think we would always want to check that, and allow the$path
through otherwise?