Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Move flow in correct directory structure according to its namespace #67

Open
levice14 opened this issue Apr 13, 2016 · 7 comments
Open
Milestone

Comments

@levice14
Copy link

levice14 commented Apr 13, 2016

No description provided.

@Moshisho
Copy link

Hi @Bonczidai , Please provide more details on this enhancement.

@levice14
Copy link
Author

say you have a flow with namespace io.cloudslang.docker under folder io/cloudslang/cloud/paas -- folder structure does not match namespace -- should move it to io/cloudslang/docker

@Moshisho
Copy link

That part I understand, but do I show a notification or actually move the files to the correct folders on some event?

@levice14
Copy link
Author

it's up to your imagination - maybe you should trigger the action using a button or key combination -- it also depends on Atom capabilties

@Moshisho
Copy link

OK, Thanks! I'll check it out.

@Moshisho
Copy link

After researching this, main conclusion is that more time is needed ;) (it requires a change of how the package is loaded) :

  1. Need to add lib folder and a coffee script file in it to run on package load. info info2
  2. Direct to this file from package.json -> 'main' key (e.g. "main": "./lib/my-package",)
  3. Subscribe to event of changing namespace. Perhaps this can help.
  4. Add event handler for it and check for file existence.
  5. In case of non matching file-path <-> namespace, notify user.
    I'm not sure if you can actually change the folder structure since it's javascript and files are in use, which can lead to problems... anyways, a notification is the way to go, IMHO.

@levice14
Copy link
Author

👍

@meshipeer meshipeer added this to the Backlog milestone Apr 18, 2016
@meshipeer meshipeer modified the milestones: 1.0-Stabilization, Backlog Aug 21, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants