lambtron / lambtron/medium-cli
Publishing error
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 85
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Hi Andy @lambtron
First, thanks for creating this very useful app. Like you , I wish if I could publish Medium from CLI
I installed it thru npm and looks every thing is working fine except for the publishing .. here is a complete view of what I did .. Please advise if I am missing anything
`bash-4.3$ pwd
/home/ajain/buzzfeed
bash-4.3$ medium login
medium · Please open https://medium.com/me/settings in your browser.
· At the bottom of the page, under Integration Tokens, copy
· this description:
· "Medium-CLI basic publishing access."
· Then generate the new token and copy it.
Paste your Integration Token here:
#####################################################################
· Authenticating into Medium..
· Saved!
bash-4.3$ medium publish
(node:19796) UnhandledPromiseRejectionWarning: Unhandled promise rejection (rejection id: 1): TypeError: Cannot read property 'split' of undefined
bash-4.3$ ls
articles
bash-4.3$ cd articles/
bash-4.3$ ls
test-post-from-medium-cli
bash-4.3$ cd test-post-from-medium-cli/
bash-4.3$ ls
index.md
bash-4.3$ cat index.md
title: test post from medium command line interface
tags:
canonicalUrl:
publishStatus: draft
license: all-rights-reserved
Testing a post from medium command line interface
bash-4.3$ `
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure with medium publish from an article directory containing index.md, using the command sequence and front matter shown in the issue. Trace the CLI's publish entry point to find where the undefined value reaches split; done means this example no longer produces the unhandled rejection and publishing reports a clear result.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- cli
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100