Some minor enhancements

[sw-carlos-cristobal]

• Adding an option to force sorting by the due date (otherwise the items are displayed however the API returns the data unsorted)
• Adding the due date to the lovelace card
• Adding an option to specify the ordering by due dates (ascending/descending order)
• Adding an option to specify the amount of days in the future to filter for the task list

[grinstantin]

Won't there be a problem with margins if item's description and due are empty?

[sw-carlos-cristobal]

Using ? as a ternary operator is safe to use to check if those are null and to render null html if so, otherwise render the corresponding data with it. This allows the card to have all 3 of these properties as optionals.

The css could probably use a little work as I'm very amateur with front-end code so it's a little rough:

[grinstantin]

What I'm trying to say is that if description and due fields are empty, content will be rendered in a <span> with todoist-item-content class, which has top and bottom margins.

[grinstantin]

I don't think this is the worst option:

${item.description || item.due
    ? html`<span class="todoist-item-content">${item.content}</span>
        <span class="todoist-item-description">${[item.description, item.due?.date].filter().join(' | ')}</span>`
    : item.content}

I would be very grateful if you could test it. I'm in the process of moving and my home server with Home Assistant installed has not yet moved to a new home.

[sw-carlos-cristobal]

Yeah I can give it a shot sometime this week - I should have more time this weekend

[sw-carlos-cristobal]

Seems like it's behaving about the same as the other code I think.

Your code:

My previous code:

[grinstantin]

I think it's just cache. In my code, description and due.date are separated by a vertical bar.

[sw-carlos-cristobal]

Ah yeah I see that now, I'll try again soon(ish)

[DannyFeliz]

@sw-carlos-cristobal did you have some time to take a look at this?