# Maintainer Documentation
Read below information that is only needed by maintainers of the `godot-playfab` project - not by general users.
## Setup
In order to run integration tests, you need to set two Environment Variables for login credentials of an existing user:
* `GODOT_PLAYFAB_TEST_USER`
* `GODOT_PLAYFAB_TEST_PASSWORD`
## Using the Model Creator
The Model Creator is a simple tool to allow you to quickly create models for PlayFab based on [PlayFab's REST API documentation](https://docs.microsoft.com/en-us/rest/api/playfab/admin/?view=playfab-rest).
Open a model definition in the browser and fill in title and data according to the image below:
This will not always generate perfect models. Specifically Type hints are likely to not compile. Either because there was an oversight on implementing the Model Creator, or because the docs are broken or you need to create another, downstream Model.
While it is not perfect, it still saves a *ton* of time.
## Implementing a Model with an Array of Objects
Some Request models have properties, which are arrays of Objects.
If the elements in this array will be custom classes in Godot, serialization of them will fail!
In order for them to correctly (de-)serialize, you need to do the following steps:
1. Create a new Class, inheriting from `AbstractJsonSerializableCollection`.
It is important, to also add a type hint for the type of the items.
This type hint needs to be initialized on construction (`_init()`).
### Example:
Given you want to create a collection for items of type `StatisticUpdate`, this is how your class should look like:
````gdscript
extends AbstractJsonSerializableCollection
class_name EventContentsCollection
func _init():
_item_type = EventContents
````
2. Instead of an `Array`, the property should use the newly created collection class. See the `Events` property below:
````gdscript
extends JsonSerializable
class_name WriteEventsRequest
# Collection of events to write to PlayStream.
var Events: EventContentsCollection
func _init():
Events = EventContentsCollection.new()
````
> ⚠️ Please be advised: Failure to implement this properly will lead to issues when deserializing!
## Git Commit Guidelines
We have very precise rules over how our git commit messages can be formatted. This leads to **more
readable messages** that are easy to follow when looking through the **project history**. But also,
we use the git commit messages to **generate the AngularJS change log**.
The commit message formatting can be added using a typical git workflow or through the use of a CLI
wizard ([Commitizen](https://github.com/commitizen/cz-cli)). To use the wizard, run `yarn run commit`
in your terminal after staging your changes in git.
### Commit Message Format
Each commit message consists of a **header**, a **body** and a **footer**. The header has a special
format that includes a **type**, a **scope** and a **subject**:
```
():