Change Details

## Overview If a user creates a post locally, while not logged in (authenticated). Then later authenticates, they can not delete the previously created local post. ## Background The CLI does not report any error, which leads the user to believe the post was deleted. However on running `writeas posts`, `list` in previous versions, the post remains. In fact visiting the URL does confirm it still exists. ## Implementation The CLI should actually delete the post from the server as well as remove the line from the `posts.psv` file. If there is some error along the way it should be reported back to the user.

## Overview If a user creates a post locally, while not logged in (authenticated). Then later authenticates, they can not delete the previously created local post. ## Background The CLI does not report any error, which leads the user to believe the post was deleted. However on running `writeas posts`, `list` in previous versions, the post remains. In fact visiting the URL does confirm it still exists. ## Implementation The CLI should actually delete the post from the server as well as remove the line from the `posts.psv` file. - If there is some error along the way it should be reported back to the user. (CLI) - WriteFreely should check for a provided token before user auth on deletes.

## Overview If a user creates a post locally, while not logged in (authenticated). Then later authenticates, they can not delete the previously created local post. ## Background The CLI does not report any error, which leads the user to believe the post was deleted. However on running `writeas posts`, `list` in previous versions, the post remains. In fact visiting the URL does confirm it still exists. ## Implementation The CLI should actually delete the post from the server as well as remove the line from the `posts.psv` file. - If there is some error along the way it should be reported back to the user. (CLI) - WriteFreely should check for a provided token before user auth on deletes.