warns when an import@ form is not found

[drzraf]

Blueprint override system is not that simple.
When a file is located in the wrong directory, wrong directory structure, or with an extension mismatch like .yml instead of .yaml, then import@ is simply ignored.
In -dev mode this is frustrating: an error message about locations searched for or at the very least a warning about import failure would really help.

thank you

[drzraf]

Another afternoon lost because of this.

[mahagr]

@drzraf This should be fixed for Toolbox 1.5.0; it will now throw an error if imports or extends fail. However, it will not fail if the blueprint file doesn't exist.