You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It might be nice if the path resolution logic for a config allowed for paths relative to that config file (e.g. to reference scripts within that directory) as opposed to the full path within either the repo or the search path setup by the user config.
Minor adjustments to both display in vscode and quiet some pylint
warnings.
Note: in the future I'd like to get some changes from #330 incorporated
to allow more self-contained config examples, with relative paths
support, added, which means changing a pile of APIs, in which case we
can probably make all of these require named position values and remove
those exceptions.
It might be nice if the path resolution logic for a config allowed for paths relative to that config file (e.g. to reference scripts within that directory) as opposed to the full path within either the repo or the search path setup by the user config.
Forked off from #313
The text was updated successfully, but these errors were encountered: