Unavailable. Nobody can download this version any more, with elm or with the Lamdera compiler: github.com/tricycle/morty-api is gone (deleted or private); Software Heritage not asked yet (this run's --swh-calls were used up); no fork with tag 3.0.0 found (9 same-name repos checked); no cached copy. Use another version.
This library provides all the models you'll get back from the MortyAPI.
A Kanban lane - effectively the lane representing a single user.
Returned as part of the KanbanLanes record.
The whole Kanban board.
The "data" content of the JSON API compliant response.
The full JSON compliant response.
A stage in the Kanban board - meta, to estimate, to do, in progress, delivered and accepted are all instances of this.
The possible statuses a KanbanStage can have.
The raw fields from the API, just for decoding purposes.
A task with only the properties required to render the Kanban board.
The different task priorities with unique display properties
The different types a kanban task can be.
A Kanban board user, represented by a lane.
The record type returned by asking Morty for a Task via MortyAPI.Commands.getTasksCommand or
MortyAPI.Commands.getTaskCommand.
The record type returned by asking Morty for Teams via MortyAPI.Commands.getTeamsCommand
The record type returned by asking Morty for Teams via MortyAPI.Commands.getTeamsCommand and
representing the team members in the team
The "data" content of the JSON API compliant response.
The full JSON compliant response.
The record type returned by asking Morty for the current user via
MortyAPI.Commands.getUserCommand. It is also how the user is represented in the Task record.
The Approach to a task. Used to create a new approach or return a list of existing approaches when you retrieve a task.