Class: Foobara::Auth::DeleteApiKey
- Defined in:
- foobara-auth-0.1.1/src/delete_api_key.rb
Constant Summary
Constants included from TruncatedInspect
Instance Attribute Summary collapse
-
#user ⇒ Object
Returns the value of attribute user.
Attributes included from CommandPatternImplementation::Concerns::Subcommands
Attributes included from CommandPatternImplementation::Concerns::Runtime
#exception, #outcome, #raw_result
Attributes included from CommandPatternImplementation::Concerns::Errors
Attributes included from CommandPatternImplementation::Concerns::Inputs
Instance Method Summary collapse
- #delete_token ⇒ Object
- #execute ⇒ Object
- #load_records ⇒ Object
-
#remove_api_key_from_user ⇒ Object
should Foobara do this automatically? Or at least support it? Similar to CASCADE in SQL.
Methods inherited from Command
Methods included from Concern
foobara_class_methods_module_for, foobara_concern?, included
Methods included from CommandPatternImplementation::Concerns::DomainMappers
#domain_map, #domain_map!, #run_mapped_subcommand!
Methods included from CommandPatternImplementation::Concerns::Subcommands
Methods included from CommandPatternImplementation::Concerns::Entities
Methods included from CommandPatternImplementation::Concerns::Transactions
Methods included from NestedTransactionable
#auto_detect_current_transactions, #commit_transaction, #commit_transaction_if_open, #open_transaction, #opened_transactions, #relevant_entity_classes, relevant_entity_classes_for_type, #relevant_entity_classes_for_type, #rollback_transaction, #transactions, #use_transaction, with_needed_transactions_for_type
Methods included from CommandPatternImplementation::Concerns::StateMachine
Methods included from CommandPatternImplementation::Concerns::Callbacks
#state_machine_callback_registry
Methods included from CommandPatternImplementation::Concerns::Runtime
#halt!, #run, #run!, #success?
Methods included from CommandPatternImplementation::Concerns::Errors
Methods included from CommandPatternImplementation::Concerns::Inputs
#cast_and_validate_inputs, #initialize, #method_missing, #respond_to_missing?, #respond_to_missing_for_inputs?
Methods included from CommandPatternImplementation::Concerns::ResultType
Methods included from CommandPatternImplementation::Concerns::InputsType
Methods included from TruncatedInspect
Dynamic Method Handling
This class handles dynamic methods through the method_missing method in the class Foobara::CommandPatternImplementation::Concerns::Inputs
Instance Attribute Details
#user ⇒ Object
Returns the value of attribute user.
26 27 28 |
# File 'foobara-auth-0.1.1/src/delete_api_key.rb', line 26 def user @user end |
Instance Method Details
#delete_token ⇒ Object
41 42 43 |
# File 'foobara-auth-0.1.1/src/delete_api_key.rb', line 41 def delete_token token.hard_delete! end |
#execute ⇒ Object
14 15 16 17 18 19 |
# File 'foobara-auth-0.1.1/src/delete_api_key.rb', line 14 def execute remove_api_key_from_user delete_token nil end |
#load_records ⇒ Object
21 22 23 24 |
# File 'foobara-auth-0.1.1/src/delete_api_key.rb', line 21 def load_records super self.user = Types::User.that_owns(token, :api_keys) end |
#remove_api_key_from_user ⇒ Object
should Foobara do this automatically? Or at least support it? Similar to CASCADE in SQL
29 30 31 32 33 34 35 36 37 38 39 |
# File 'foobara-auth-0.1.1/src/delete_api_key.rb', line 29 def remove_api_key_from_user api_keys = user.api_keys if api_keys.include?(token) user.api_keys = api_keys - [token] else # :nocov: raise "User has no such api key" # :nocov: end end |