applications library
The v4 applications family: its endpoints, bound class, path templates and views.
Import it with a prefix, import 'package:exsited/applications.dart' as applications;,
because families declare the same top-level names and a Dart export can
neither rename nor prefix them.
Classes
- ApplicationsResource
- The applications endpoints with client already applied.
- ApplicationsUrls
- SettingsApplication
-
The settings application body, under
application. - SettingsApplicationList
-
One page of
SettingsApplicationrecords, underdata.
Functions
-
createSettingsApplication(
ExsitedClient client, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsApplication> > -
POST /api/{api_version}/settings/applications -
deleteSettingsApplication(
ExsitedClient client, Object applicationId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< Object?> > -
DELETE /api/{api_version}/settings/applications/{application_id} -
getSettingsApplication(
ExsitedClient client, Object applicationId, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsApplication> > -
GET /api/{api_version}/settings/applications/{application_id} -
getSettingsApplications(
ExsitedClient client, {Map< String, Object?> ? queryParams, bool? raiseOnError, String? responseFormat}) → Future<ApiResponse< SettingsApplicationList> > -
GET /api/{api_version}/settings/applications -
updateSettingsApplication(
ExsitedClient client, Object applicationId, Object payload, {bool? raiseOnError, String? responseFormat}) → Future< ApiResponse< SettingsApplication> > -
PATCH /api/{api_version}/settings/applications/{application_id}