programming

Last time I mentioned that we had two related issues to fix: What we were displaying as HTML was not in fact valid HTML;The code generating that "HTML" from a list of tasks was the least-tested part of Veery.Steps to fixing those problemsCreate a folder, and a file

Now we can just put the pieces together and add a function to serve a Web display of a list of tasks: @route("/") def list_tasks(task_repository: TaskRepository = repo): return "<br>".join([str(task) for task in task_repository.get_all_tasks()]) No, this is not valid

I still, every time, get a thrill from seeing a Web interface to a new prototype. We're almost there. First we'll: Add the dependency on the Web framework;Remove old code;Make sure the tests still pass and the Web framework works as intended.The stepsDelete all current code from

So! We've separated the Task object from its persistence. An important practical benefit of that separation is that other parts of the code base--for example, a part that accepts and processes requests to add and delete tasks--can do their work independently of the details of that persistence. The repository is

The whole point of the last few installments, and the thousands of words (and however much study) accompanying them, has been to separate the domain and persistence layers. Yet I failed to do that. To persist or load a Task, the repository needed to turn the domain object to or

Last time I introduced a small bug (unintentionally). The test file as it existed then began with import pytest. I typed this habitually, because I usually need to import pytest in files with tests in them (we'll see why). But it's not necessary. pytest, the program I run from the

Until now we've been reading objects from our (primitive, flat-text-file) database and writing to that database and directly treating those objects as our tasks. That is: Our get_all_tasks() function gives us strings;Our other functions accept strings;That's because strings are things our database knows how to persist;

Last time I wrote a bit about tests, linked you to other writing of mine about tests, and instructed you to add a requirements.txt file to your repository. If you are new to software engineering, you probably have had some sort of headache having to do with git, your

Our task manager does stuff now, though in a primitive form. I ended the last installment by reflecting on the tons and tons of stuff that this software does not do and that we would like it to do. Testing software is an essential part of improving it. (Here are