A small command-line interface to interact with a toy Jira clone, IronJira.

A small command-line interface to interact with a toy Jira clone, IronJira.

Represents a comment on a [Ticket](Ticket) Wraps a string and checks that it is not empty when set

Error if a comment cannot be created

A ticket that was deleted from the store. Using the new-type pattern to distinguish it from [Ticket](Ticket).

Rust's enums are perfect for this usecase. Enum stands for enumeration: a type encoding the constraint that only a finite set of values is possible. E

Structs, enums and functions defined in a module are visible to all other structs, enums and functions in the same module - e.g. we can use `Ticket` i

We will begin our journey of building our own JIRA clone defining the cornerstone of JIRA's experience: the ticket. For now we want to limit ourselves

Re-defining Ticket here because methods who need to access private fields have to be defined in the same module of the struct itself, as we saw in the

Ticket have two purposes in JIRA: capturing information about a task and tracking the completion of the task itself. Let's add a new field to our `Ti

The content of the ticket, not yet saved in the [TicketStore](TicketStore::create).

The content of the ticket, to be updated in the [TicketStore](TicketStore::create).

Feel free to add more fields to `TicketStore` to solve this koan!

First we will create a TicketStore struct, with a `data` field of type HashMap. HashMap is a *generic* struct: we need to specify two types, one for

Let's turn our attention again to our `TicketStore`. We can create a ticket, we can retrieve a ticket. Let's implement a `list` method to retrieve al

There are only two pieces missing: deleting a ticket and updating a ticket in our `TicketStore`. The update functionality will give us the possibility

The title of a [Ticket](Ticket) Wraps a string and checks that it's not empty when set

Error if a title cannot be created