Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: overhauling error handling to support the new api error responses #218

Merged
merged 2 commits into from
Jul 15, 2020

Conversation

erunion
Copy link
Member

@erunion erunion commented Jul 15, 2020

🧰 What's being changed?

This overhauls every command to support the new way we're handling errors within the API and allowing us to surface Metrics log IDs in the console for API failures

@erunion erunion added the enhancement New feature or request label Jul 15, 2020
@@ -49,6 +50,9 @@ exports.run = function (opts) {
}

const files = fs.readdirSync(folder).filter(file => file.endsWith('.md') || file.endsWith('.markdown'));
if (files.length === 0) {
return Promise.reject(new Error(`We were unable to locate Markdown files in ${folder}.`));
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Adding this error message because if a user tries to use rdme docs with a directory that has subdirectories containing Markdown, we currently can't handle those Markdown files as rdme docs can't handle category creation and management right now.

https://app.asana.com/0/1178132843162889/1183431246035890/f

@erunion erunion merged commit 0a5e92b into master Jul 15, 2020
@erunion erunion deleted the feat/use-new-errors branch July 15, 2020 17:54
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants