Is there a way in the UI to change where the Features are being exported to?
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | features_custom_path-2693123-7.patch | 3.06 KB | mpotter |
| #5 | features_custom_path-2693123-5.patch | 2.69 KB | mpotter |
Is there a way in the UI to change where the Features are being exported to?
| Comment | File | Size | Author |
|---|---|---|---|
| #7 | features_custom_path-2693123-7.patch | 3.06 KB | mpotter |
| #5 | features_custom_path-2693123-5.patch | 2.69 KB | mpotter |
Comments
Comment #2
mpotter commentedNot in the UI. It's a config variable export.folder in features.settings.yml. Changing this to a feature request.
Comment #3
mxr576It would be much better if we could specify each feature's location on the generation UI, just as we could in D7.
Comment #4
duaelfr#2741241: Export existing feature where it is currently, not necessarily in modules/custom has been closed as duplicate of this issue.
Just adding for the record: the default value of that field should be the current feature location like it was in D7.
Comment #5
mpotter commentedHere is a patch that does a first pass at this. Added a Path field to the Edit form that will override the export directory. However, this needs to be a relative path to the Drupal root. Being able to specify a path outside the root would require more extensive changes regarding the use of $this->root. The only use-case for this would be to write to the temporary directory and maybe that should be an option rather than any arbitrary file path.
But for now, here we go.
Comment #7
mpotter commentedAhh, missed a line that was setting the initial directory. Try this.
Comment #9
mpotter commentedCommitted to 1edc3b9.
Comment #10
mpotter commented