'Fetch Lightning' now puts files in src/aura, also doesn't get .manifest file

[rrcook]

Windows 7 64 bit, latest Lightning plugin and force cli
Doing 'Fetch, Lightning' and picking a component. Previously components were put in metadata/aura directory, and .manifest file was fetched as well. Now components are put in src/aura, with no .manifest file.

[GustavoGus]

Hi,

Same here.

MavensMate for Sublime Text v6.0.3.
Windows 7 64 bit
I also re-downloaded CLI and re-create the project.
The lightning plugin is also up to date.

Hope we can find a workaround soon. :(

Gustavo

[GustavoGus]

The only workaround I could find is:

1 - Lightning Fetch all your bundles. In my case it creates a the "aura" folder on "src".
2 - Close Sublime.
3 - Create by yourself the "metadata" folder.
4 - Move "aura" folder inside the "metadata" folder.

Then you can edit your components and save them.

Hope this can help meanwhile we get a solution.

[rrcook]

I do something similar. Pure force CLI "force fetch -t aura" into a totally separate directory.
Then copy .manifest files, or components, into my metadata/aura, then edit & save from inside plugin.

[dcarroll]

This is a bug. The plugin actually tries to determine what the file type is based on directory structure. A change to the CLI has made that a big more difficult to determine. I'll see if I can get a fix in soon.

[dcarroll]

Ok, maybe not a bug. MavensMate may be confusing the plugin. If you have a src folder, then the cli will download your metadata to that folder, otherwise, it should download to metadata, or create metadata and download to metadata.

If MavensMate is using "src" (as does the Eclipse IDE) then you should be seeing the actual metadata (definitions) in the src folder. Still need to test the missing .manifest.

[rrcook]

I have a project with src and metadata folders. I use the Eclipse IDE for src (classes, pages, etc.) and sublime + plugin for the lightning components in metadata. With the setup, until recently the plugin fetched lightning components into metadata.
I do have MavensMate installed in my sublime but no longer use it. Should I remove it?

[dcarroll]

I have not done any testing with MavensMate. You could try using it in a
new directory and let me know what the behavior is, without invoking
MavensMate of course.

On Fri, Jun 17, 2016 at 6:40 PM, Richard Cook notifications@github.com
wrote:

I have a project with src and metadata folders. I use the Eclipse IDE for
src (classes, pages, etc.) and sublime + plugin for the lightning
components in metadata. With the setup, until recently the plugin fetched
lightning components into metadata.
I do have MavensMate installed in my sublime but no longer use it. Should
I remove it?

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#40 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHGHpjGXhcFAjmIlgMWo8Q6MlMJacdzks5qM0ylgaJpZM4It1ri
.

Thanks,
Dave

[rrcook]

Windows 7 64 bit.
I've uninstalled MavensMate (I'm currently not using it).
I made a new directory, opened it in Sublime Text.
Logged in, fetched a Lightning component. Plugin made a metadata\aura directory and put the component there.
Quit ST, made a src directory off of the new directory, started ST, logged in, fetched a component. Plugin made src\aura directory and put the component there.
In both cases it pulled down the .manifest file.

I've had my project with the directory structure (both metadata and src directories) for a while; fetching components into src\aura is a new phenomenon.

[dcarroll]

Ok, that's helpful. What behavior are you looking to see?

On Tue, Jun 21, 2016 at 9:38 AM, Richard Cook notifications@github.com
wrote:

Windows 7 64 bit.
I've uninstalled MavensMate (I'm currently not using it).
I made a new directory, opened it in Sublime Text.
Logged in, fetched a Lightning component. Plugin made a metadata\aura
directory and put the component there.
Quit ST, made a src directory off of the new directory, started ST, logged
in, fetched a component. Plugin made src\aura directory and put the
component there.
In both cases it pulled down the .manifest file.

I've had my project with the directory structure (both metadata and src
directories) for a while; fetching components into src\aura is a new
phenomenon.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#40 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHGHjAOg3JNNhwHGtG_hDeABAH9V6kqks5qOBOGgaJpZM4It1ri
.

Thanks,
Dave

[rrcook]

In a project or directory where there are both metadata and src directories, fetching a lightning component puts it in the metadata directory. This is the behavior that happened previously. I've had this directory structure for months, and until very recently a lightning fetch would put components in the metadata\aura directory.
Also, this is where the force.com cli puts lightning components when doing "force fetch -t aura"

[dcarroll]

Ok, I understand, so in the case of the presence of both meta and src,
default to meta, yeah?

On Tue, Jun 28, 2016 at 10:33 AM, Richard Cook notifications@github.com
wrote:

In a project or directory where there are both metadata and src
directories, fetching a lightning component puts it in the metadata
directory. This is the behavior that happened previously. I've had this
directory structure for months, and until very recently a lightning fetch
would put components in the metadata\aura directory.
Also, this is where the force.com cli puts lightning components when
doing "force fetch -t aura"

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
#40 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAHGHkk5ITorrKAJzk6Eba2CnQw97NNcks5qQVrRgaJpZM4It1ri
.

Thanks,
Dave

[dcarroll]

#TODO Currently, GetSourceDir is dependent on the order of the two member slice that contains the possible directory names, "src", "metadata". Need to check to see if both exist rather than returning upon first match to slice.