Skip to content
This repository was archived by the owner on May 2, 2022. It is now read-only.

Conversation

@ehmicky
Copy link
Contributor

@ehmicky ehmicky commented Sep 22, 2020

Fixes #39.

If the user is configuring a custom build.edge_handlers property, but the path points to a non-existing file, this plugin currently fails with a scandir: ... error message, which is not clear. This PR adds a validation check to report this user error with a clearer message. It also includes an integration test.

Note: when build.edge_handlers is not specified, constants.EDGE_HANDLERS_SRC defaults to "edge-handlers". However, this plugin is skipped if there is no edge-handlers directory. So that validation check only has an impact when the user configures build.edge_handlers.

@ehmicky ehmicky added the type: feature code contributing to the implementation of a feature and/or user facing functionality label Sep 22, 2020
@ehmicky ehmicky self-assigned this Sep 22, 2020
Copy link
Contributor

@shortdiv shortdiv left a comment

Choose a reason for hiding this comment

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

LGTM!

@ehmicky ehmicky merged commit 5c883f7 into master Sep 22, 2020
@ehmicky ehmicky deleted the feat/validate-edge-handlers-config branch September 22, 2020 20:06
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

type: feature code contributing to the implementation of a feature and/or user facing functionality

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Check for wrong edge handlers directory

3 participants