Skip to content

Addition to spec #2281

@HubertKauker

Description

@HubertKauker

In the section on Functionality, the current spec says that a New todo is appended to the todo list. It should also be said that the focus remains on the cleared input field and that the new todo is displayed at the bottom of the list. That practice, however, has the disadvantage, that in many cases the new entry is not visible and the user of the app has to scroll down the page in order to see it. Would it not be more practical to require that new entries are displayed at the top of the list?

When a todo is to be deleted from the list, should the spec say something about whether a confirmation by the user is required or not?

Should the spec allow a completed item to be edited or not? I would plead to disallow it.

What about id's? Is that not an implementation detail which must not necessarily be mentioned in the spec? The section of Persistence says to persist them. But why? They are not visible in the interface. Or should they be visible?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions