last one, I promise. next time I'll use the mocks.

if using unclaimed works, how does this help sound?

what about using unclaimed for the local unsynced posts in this list?

ok cool, I'll make the change

I think for this one, it will be both.

pinged the wrong matt on the PR for this. Also should be open until that is merged.

this is already implemented as NewClientWith

I also put up #30 CLI which returns the errors during delete to the user. Then this can close.

This is required to test the fix for T612 on the WriteFreely side

I think I found the issue, the logic in this function on writefreely appears to check first if the accesstoken or user were found and proceed with that authentication, which will result in no affected rows. Lines 741-788, then an else which assumes the editToken instead.

I found in go-writeas:

Additional questions we might want to answer:

• should there be a confirmation/warning if we are importing all posts?
• should we ask one at a time?
  • if so should we pull the title and an excerpt during confirmation?

thanks @matt, they aren't verbose enough though. Only requests and their http status + method.

is it possible to see the server application logs for development.write.as

I'm getting back a 403 forbidden with the correct token, it must be getting returned by go-writeas in writeas.go c.delete().

In T602#9361, @robjloranger wrote:

found a cool little library for neat tabbed columns

https://github.com/ryanuber/columnize

I edited the task because deleting of both published and write.as anonymous posts already works. just not the local anonymous ones, which I guess are the true anonymous posts.

I'm pretty sure this is already implemented. I'm going to look over the current version-two code as I write and think out loud.

current status as or PR, also supports -md

i think local posts are the unclaimed posts for the user at the cli. it that correct?

created a mock for the detailed output which i think would be good behind the flag d, detail M5

@matt by unsynced posts, do you mean unclaimed? i.e. https://developers.write.as/docs/api/#claim-posts

😄

so the current implementation I have gets the local posts and then the remote.

perhaps not, of course generally speaking they should always return their errors.

in v2 branch

this needs to be updated in both:

• collection_test.go
  • TestGetCollectionPosts
  • TestGetCollectionPost
• post_test.go
  • TestCreatePost
  • ExampleClient_CreatePost

wrong password 😵

resolved in

I was also going to add a flag like detail, d to include more output like the excerpt and collection.

resolved in https://github.com/writeas/writeas-cli/pull/27