Skip to content
This repository has been archived by the owner on Feb 18, 2024. It is now read-only.

Improve error messaging for middleware used with no entry point #386

Merged
merged 3 commits into from
Oct 31, 2017
Merged

Improve error messaging for middleware used with no entry point #386

merged 3 commits into from
Oct 31, 2017

Conversation

eliperelman
Copy link
Member

Fixes #384.

@eliperelman eliperelman requested a review from a team October 29, 2017 01:42
Copy link
Member

@edmorley edmorley left a comment

Choose a reason for hiding this comment

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

Look great! :-)

Copy link
Member

@edmorley edmorley left a comment

Choose a reason for hiding this comment

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

Actually, I don't suppose you could add a test here too, seeing as we already have some prior art for testing options.entry?

@eliperelman
Copy link
Member Author

@edmorley I added a test, but in doing so changed a few things. I didn't want to put references to the CLI in an error generated by the API, so I made it generic, then re-handled in the CLI. To make this consistent across all commands, I made each CLI command call a common base which removes a lot of the boilerplate that every command was doing.

Hopefully this brings more simplicity and consistency to our handling from the CLI.

@edmorley
Copy link
Member

Even better! :-)

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Development

Successfully merging this pull request may close these issues.

2 participants