PcoServicesAttachmentType class Null safety

This class represents a PCO Services AttachmentType Object

Instantiation

  • This object cannot be created through the API.
  • Instantiate from existing JSON data using the PcoServicesAttachmentType.fromJson() constructor.
  • Load an instance from the API using one of the static methods defined on this class.

Usage

  • Fields exposed by the API are readable through getter methods.
  • Fields writable by the API are exposed through setter methods.
  • Original json data is exposed through the read-only attributes map.
  • Additional data is available through the read-only links and relationships maps.
  • Available relationships / includes are exposed through typed getters.

Description

Create an Attachment Type for each type of file you might want only specific people to see. When you attach a file, you can specify an attachment type to then be able to link the file to a position.

Attributes (and permissions)

  • id (ro) -> PCO: id
  • name (ro) -> PCO: name
  • aliases (ro) -> PCO: aliases
  • isCapoedChordCharts (ro) -> PCO: capoed_chord_charts
  • isChordCharts (ro) -> PCO: chord_charts
  • exclusions (ro) -> PCO: exclusions
  • isLyrics (ro) -> PCO: lyrics
  • isNumberCharts (ro) -> PCO: number_charts
  • isNumeralCharts (ro) -> PCO: numeral_charts
  • isBuiltIn (ro) -> PCO: built_in

Edges and Actions

Outbound Edges: NONE

Inbound Edges:

Actions: NONE

Raw Data Object Example

{
  "type": "AttachmentType",
  "id": "1",
  "attributes": {
    "name": "string",
    "aliases": "string",
    "capoed_chord_charts": true,
    "chord_charts": true,
    "exclusions": "string",
    "lyrics": true,
    "number_charts": true,
    "numeral_charts": true,
    "built_in": true
  },
  "relationships": {
    "attachment_type_group": {
      "data": {
        "type": "AttachmentTypeGroup",
        "id": "1"
      }
    }
  }
}
Inheritance

Constructors

PcoServicesAttachmentType({String? id, String? name, String? aliases, bool? isCapoedChordCharts, bool? isChordCharts, String? exclusions, bool? isLyrics, bool? isNumberCharts, bool? isNumeralCharts, bool? isBuiltIn, Map<String, List<PcoResource>>? withRelationships, List<PcoResource>? withIncluded})
Create a new PcoServicesAttachmentType object. This object cannot be created with the API
factory
PcoServicesAttachmentType.empty()
Create an empty instance of this class. This is only useful when an endpoint requires related or included data.
PcoServicesAttachmentType.fromJson(Map<String, dynamic> data, {List<Map<String, dynamic>>? withIncluded})

Properties

aliases → String
read-only
api → PlanningCenter
planning center resources must be tied to an api
read-onlyinherited
apiEndpoint → String
read-onlyinherited
apiPath → String
PcoResources include their own path as a link object but this might be null if we haven't created/fetched the object yet Child classes should redefine this getter to allow for manual path overrides
read-onlyoverride
apiVersion → String
child classes can override these getters which will allow methods in this class to see static variables from child classes
read-onlyoverride
attributes → ReadOnlyMapView<String, dynamic>
contains the underlying attributes returned by the api and allows a user to access arbitrary data in the attributes by actual api name
read-onlyinherited
canCreate → bool
read-onlyoverride
canDestroy → bool
read-onlyoverride
canUpdate → bool
read-onlyoverride
createAllowed → List<String>
read-onlyoverride
createdAt → DateTime
read-onlyinherited
createPathTemplate → String
read-onlyoverride
defaultPathTemplate → String
read-onlyoverride
exclusions → String
read-only
fetched ↔ bool
indicate whether an item is full or partial
read / writeinherited
hashCode → int
The hash code for this object.
read-onlyinherited
id → String?
read-onlyinherited
included → List<PcoResource>
contains included items parsed into objects
read-onlyinherited
isBuiltIn → bool
read-only
isCapoedChordCharts → bool
read-only
isChordCharts → bool
read-only
isLyrics → bool
read-only
isNumberCharts → bool
read-only
isNumeralCharts → bool
read-only
contains the links data returned by the api if present
read-onlyinherited
name → String
read-only
needsSave → bool
read-onlyinherited
pcoApplication ↔ String
latefinalinherited
relationships → ReadOnlyMapView<String, List<PcoResource>>
contains relationships parsed into objects even though the api sends relationship objects as Maps or Lists we always put them into lists for consistency
read-onlyinherited
resourceType ↔ String
all planning center resources must have a type
latefinalinherited
runtimeType → Type
A representation of the runtime type of the object.
read-onlyinherited
slug → String
read-onlyinherited
updateAllowed → List<String>
read-onlyoverride
updatedAt → DateTime
read-onlyinherited

Methods

coerceDouble(dynamic a) → double
inherited
coerceInt(dynamic a) → int
inherited
delete() → Future<PlanningCenterApiResponse<PlanningCenterApiData>>
inherited
filteredAttributes(List<String> allowedKeys) → Map<String, dynamic>
inherited
fromJson(Map<String, dynamic> data, {List<Map<String, dynamic>>? withIncluded}) → dynamic
Takes a full JSON:API Response Object (the contents of a "data" field) will clear and update id, apiPath, attributes and _relationships
inherited
handleIncludes(List<Map<String, dynamic>> included) → void
This function populates the relationships with typed resource objects based on the data in the included map of the json.
inherited
handleItem(Map<String, dynamic> data) → PcoResource?
inherited
handleRelationships(Map<String, dynamic> items, [List<Map<String, dynamic>> included = const []]) → Map<String, List<PcoResource>>
inherited
noSuchMethod(Invocation invocation) → dynamic
Invoked when a non-existent method or property is accessed.
inherited
save({Map<String, PcoResource>? withRelated, List<PcoResource>? withIncluded}) → Future<PlanningCenterApiResponse<PlanningCenterApiData>>
Many Planning Center endpoints allow or require additional relationships and/or included items to be sent with a create/update operation. Since these cannot always be determined by the automatic code generation, they may be included as arguments to the save operation.
inherited
toCreateResource() → Map<String, dynamic>
create the attributes Map for this object without the id field using only the attributes allowed in create (post) operations
inherited
toDataMap({Map<String, PcoResource>? withRelated, List<PcoResource>? withIncluded}) → Map<String, dynamic>
create a json-api Map for this object automatically selecting create or update based on the existence of the id field. Will result in something like this:
inherited
toIdResource() → Map<String, dynamic>
returns the simplest representation of this resource with only the type and the id:
inherited
toJson({dynamic includeAttributes = true, dynamic includeRelationships = false}) → Map<String, dynamic>
Some api requests only want the type and id of an object. In those cases, set includeAttributes to false or call toIdResource instead.
inherited
toString() → String
A string representation of this object.
inherited
toUpdateResource() → Map<String, dynamic>
create the attributes Map for this object using only the attributes allowed in update (patch) operations
inherited

Operators

operator ==(Object other) → bool
The equality operator.
inherited

Static Properties

canInclude → List<String>
possible includes with parameter ?include=a,b
read-only
canOrderBy → List<String>
possible orderings with parameter ?order=
read-only
canQuery → List<String>
possible queries using parameters like ?wherekey=value or ?wheregt|lt=value
read-only

Static Methods

get({String? id, PcoServicesAttachmentTypeQuery? query, bool getAll = false}) → Future<PcoCollection<PcoServicesAttachmentType>>
Will get a PcoCollection of PcoServicesAttachmentType objects (expecting many) using a path like this: /services/v2/attachment_types
getAll({String? id, PcoServicesAttachmentTypeQuery? query}) → Future<PcoCollection<PcoServicesAttachmentType>>
Will get a PcoCollection containing ALL PcoServicesAttachmentType objects (expecting many) using a path like this: /services/v2/attachment_types
getSingle(String id, {PcoServicesAttachmentTypeQuery? query}) → Future<PcoServicesAttachmentType?>
Will get a single PcoServicesAttachmentType object using a path like this: /services/v2/attachment_types/[id]

Constants

kAliases → const String
'aliases'
kApiVersion → const String
'2018-11-01'
kBuiltIn → const String
'built_in'
kCapoedChordCharts → const String
'capoed_chord_charts'
kChordCharts → const String
'chord_charts'
kCreatePathTemplate → const String
'null'
kDefaultPathTemplate → const String
'https://api.planningcenteronline.com/services/v2/attachment_types'
kExclusions → const String
'exclusions'
kId → const String
'id'
kLyrics → const String
'lyrics'
kName → const String
'name'
kNumberCharts → const String
'number_charts'
kNumeralCharts → const String
'numeral_charts'
kPcoApplication → const String
'services'
kTypeId → const String
'attachment_type'
kTypeString → const String
'AttachmentType'