bwhmather / bdc-js Goto Github PK

To get some idea of how bad BDC actually is, it would be good to implement some common benchmarks.
The DB monster benchmark from the mithril examples folder looks like a good start.

https://github.com/MithrilJS/mithril.js/tree/next/examples/dbmonster
https://raw.githack.com/MithrilJS/mithril.js/master/examples/dbmonster/mithril/index.html
https://mithril.js.org/framework-comparison.html

See https://github.com/tastejs/todomvc/blob/master/app-spec.md for detailed specification.

No todos

• When there are no todos, #main and #footer should be hidden.

New todos

• New todos are entered in the input at the top of the app.
• The input element should be focused when the page is loaded, preferably by
  using the autofocus input attribute.
• Pressing Enter creates the todo, appends it to the todo list, and clears
  the input.
• Make sure to .trim() the input and then check that it's not empty before
  creating a new todo.

Mark all as completed

• The mark all completed checkbox toggles all the todos to the same state as
  itself.
• The make all completed button should be cleared after the "Clear completed"
  button is clicked.
• The "Mark all as complete" checkbox should also be updated when single todo
  items are checked/unchecked.

Item interaction

• Clicking an item checkbox marks the todo as complete by updating its
  completed value and toggling the class completed on its parent <li>
• Double-clicking an item <label> activates editing mode, by toggling the
  .editing class on its <li>.
• Hovering over the todo shows the remove button (.destroy)

Editing

• When editing mode is activated it will hide the other controls and bring
  forward an input that contains the todo title
• The item should be focused when editing starts.
• The edit should be saved on both when the enter key is pressed, and the editing class
  should be removed.
• The edit should also be saved when focus is lost.
• Make sure to .trim() the input and then check that it's not empty.
• If it's empty the todo should instead be destroyed.
• If escape is pressed during the edit, the edit state should be left and any changes be discarded.

Counter

• Displays the number of active todos in a pluralized form.
• Make sure the number is wrapped by a <strong> tag.
• Also make sure to pluralize the item word correctly: 0 items, 1 item, 2
  items. Example: 2 items left

Clear completed button

• Removes completed todos when clicked.
• Should be hidden when there are no completed todos.

Persistence

• Your app should dynamically persist the todos to localStorage.
• If possible, use the keys id, title, completed for each item.
• Make sure to use this format for the localStorage name: todos-[framework].
• Editing mode should not be persisted.

Routing

The following routes should be implemented:

• #/ (all - default)
• #/active
• #/completed (#!/ is also allowed).
• When the route changes, the todo list should be filtered on a model level
  and the selected class on the filter links should be toggled.
• When an item is updated while in a filtered state, it should be updated
  accordingly. E.g. if the filter is Active and the item is checked, it should be hidden.
• Make sure the active filter is persisted on reload.

Testcafe drags in 429 unique dependencies, 784 in total. Although these are only dragged in during development, this is a serious liability.

BDC doesn't currently do any input validation. This means that bad input, at best, results in difficult to decode exceptions from deep inside clobber. While it probably isn't possible to add validation to the prod build without exceeding 1024 bytes, it would be good to have some checks in the debug build to help during development.