class CB::TeamUpdate
- CB::TeamUpdate
- CB::TeamAction
- CB::APIAction
- CB::Action
- Reference
- Object
Defined in:
cb/team.crInstance Method Summary
-
#billing_email : String | Nil
TODO (abrightwell) - would be really nice to have some validation on this property.
-
#billing_email=(billing_email : String | Nil)
TODO (abrightwell) - would be really nice to have some validation on this property.
- #confirmed : Bool
- #confirmed=(confirmed : Bool)
- #confirmed=(str : String)
- #enforce_sso : Bool | Nil
- #enforce_sso=(enforce_sso : Bool | Nil)
- #enforce_sso=(str : String)
- #name : String | Nil
- #name=(str : String)
- #name=(name : String | Nil)
- #run
Instance methods inherited from class CB::TeamAction
format : Format
format,
format=(format : Format)format=(str : String) format=, team_id : String | Nil team_id, team_id=(str : String)
team_id=(team_id : String | Nil) team_id=
Instance methods inherited from class CB::APIAction
client : Client
client,
client=(client : Client)
client=,
run
run
Constructor methods inherited from class CB::APIAction
new(client : CB::Client, input = STDIN, output = STDOUT)
new
Instance methods inherited from class CB::Action
call
call,
input : IO
input,
input=(input : IO)
input=,
output : IO
output,
output=(output : IO)
output=
Constructor methods inherited from class CB::Action
new(input : IO = STDIN, output : IO = STDOUT)
new
Instance Method Detail
TODO (abrightwell) - would be really nice to have some validation on this property. I briefly looked into implementing a macro for it, but it an email regex is non-trivial. Need to determine what would be 'good enough' for our purposes here. So I'm going to come back to this one in a future update. For now, we'll rely on the API validation of the field.
TODO (abrightwell) - would be really nice to have some validation on this property. I briefly looked into implementing a macro for it, but it an email regex is non-trivial. Need to determine what would be 'good enough' for our purposes here. So I'm going to come back to this one in a future update. For now, we'll rely on the API validation of the field.