cjoudrey/md2medium

Clear config when access tokens are invalid

Open

#2 opened on Jul 18, 2017

View on GitHub
 (0 comments) (0 reactions) (0 assignees)Go (3 forks)github user discovery
enhancementhelp wanted

Repository metrics

Stars
 (25 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

Steps to reproduce:

  • Setup md2medium with valid API tokens.
  • Revoke an API token.
  • Run md2medium and you will see a 401 error.

When this happens we should clear the token from the config file such that the next time md2medium is run the user will be prompted for a token again.

Even better, we could prompt the user for a new token when the 401 happens.

Contributor guide

Research direction
Identify where the HTTP 401 error is handled after an API call to Medium, and add logic to remove the invalid token from the config file. Optionally, prompt the user for a new token.
Tech stack
go
Domain
cliapi
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGo
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75