TODO: is this WF-only? Or both CLIs?

Assuming the #117 fix works in your testing, after reviewing everything I do think this is the right solution.

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:

I'd say the assumed behavior will be that all posts are imported. This is the behavior on the web app, and will be the behavior on the Android app, as well.

Can you verify requests (both login and delete) are going to the right environment with some logging on your end? If they are, I'll add some logging on the dev server.

Not crucial in the short-term.

Not crucial in the short-term.

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.

I'm sending logs over from the dev server now, polled every 10 seconds. You can view on our team server with:

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

As mentioned, original task was already taken care of, so closing this.

@robjloranger Hmm, but deleting local anonymous posts was the behavior in CLI v1, no? That should already work.

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?

In T604#9443, @robjloranger wrote:

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

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

Excellent 😃

😄

I think I like the full local / remote word for now; it's clear and saves me from looking up what letters mean in the user guide.

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.

wrong password 😵

In T594#9289, @robjloranger wrote:

this will be set on the writefreely cli, the writeas cli will retain the original .writeas directory

resolved in

Paying attention to this, since I'm likely to wind up using these config files in T571 as well. Let me know if I can contribute.

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

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