mirror of
https://github.com/stripe/stripe-ruby.git
synced 2025-10-06 00:02:18 -04:00
863da48398
Adds the magic `frozen_string_literal: true` comment to every file and enables a Rubocop rule to make sure that it's always going to be there going forward as well. See here for more background [1], but the basic idea is that unlike many other languages, static strings in code are mutable by default. This has since been acknowledged as not a particularly good idea, and the intention is to rectify the mistake when Ruby 3 comes out, where all string literals will be frozen. The `frozen_string_literal` magic comment was introduced in Ruby 2.3 as a way of easing the transition, and allows libraries and projects to freeze their literals in advance. I don't think this is breaking in any way: it's possible that users might've been pulling out one of are literals somehow and mutating it, but that would probably not have been useful for anything and would certainly not be recommended, so I'm quite comfortable pushing this change through as a minor version. As discussed in #641. [1] https://stackoverflow.com/a/37799399
28 lines
799 B
Ruby
28 lines
799 B
Ruby
# frozen_string_literal: true
|
|
|
|
module Stripe
|
|
class ApplicationFee < APIResource
|
|
extend Stripe::APIOperations::List
|
|
extend Stripe::APIOperations::NestedResource
|
|
|
|
OBJECT_NAME = "application_fee".freeze
|
|
|
|
nested_resource_class_methods :refund, operations: %i[create retrieve update list]
|
|
|
|
def self.resource_url
|
|
"/v1/application_fees"
|
|
end
|
|
|
|
# If you don't need access to an updated fee object after the refund, it's
|
|
# more performant to just call `fee.refunds.create` directly.
|
|
def refund(params = {}, opts = {})
|
|
refunds.create(params, opts)
|
|
|
|
# now that a refund has been created, we expect the state of this object
|
|
# to change as well (i.e. `refunded` will now be `true`) so refresh it
|
|
# from the server
|
|
refresh
|
|
end
|
|
end
|
|
end
|