When building Vue apps, we will invariably have components that are pretty generic and don’t fit within any one feature area. For these type of components we create a global registry so they are available throughout the application.
The vue-devtools is a fantastic browser extension for Chrome and Firefox that give you direct access to component tree, state snapshots, and events. It dramatically increases developer productivity. The only problem is it won’t run in Safari.
For a long time now we’ve used Browserify for our bundling and a bunch of different npm scripts to manage other aspects of our static pipeline. The more we started doing with Vue, the more it became obvious the need to move to Webpack.
Last month, Eldarion launched the new Scaife Viewer for the Perseus Digital Library. Yesterday, I gave an online talk on the project, as part of the SunoikisisDC series of seminars on Digital Classics.
Eldarion is helping build the next version of Perseus.
The much anticipated Django 2.0 was recently released and we are updating Pinax apps, client projects, and our own sites. This offers the perfect opportunity to share our process and some of the most common issues.
Recently I updated
eldarion-ajax to have more robust tests along with 100% test coverage. I wanted to get to this point before I venture into some potentially aggressive refactoring.
For a long time, we used TravisCI and Coveralls for executing lint checkers and tests and tracking our code coverage. These are fine tools but we’ve recently switched to CircleCI and CodeCov. This is our default setup for projects.
It can be fairly common to have situations where your users need to quickly add
items to a list, edit those items, and perhaps even sort them. Ideally,
we can keep the user focused on their data and tasks rather than how to
navigate the software facilitating the work.
Code coverage is an important aspect of good engineering practice. Without it, you are flying a bit blind writing tests.