{"action":"created","issue":{"url":"https://api.github.com/repos/mattblackdev/meteor-package-intellisense/issues/1","repository_url":"https://api.github.com/repos/mattblackdev/meteor-package-intellisense","labels_url":"https://api.github.com/repos/mattblackdev/meteor-package-intellisense/issues/1/labels{/name}","comments_url":"https://api.github.com/repos/mattblackdev/meteor-package-intellisense/issues/1/comments","events_url":"https://api.github.com/repos/mattblackdev/meteor-package-intellisense/issues/1/events","html_url":"https://github.com/mattblackdev/meteor-package-intellisense/issues/1","id":377155078,"node_id":"MDU6SXNzdWUzNzcxNTUwNzg=","number":1,"title":"Support for monorepos or other non-typical folder structures","user":{"login":"arggh","id":17210302,"node_id":"MDQ6VXNlcjE3MjEwMzAy","avatar_url":"https://avatars3.githubusercontent.com/u/17210302?v=4","gravatar_id":"","url":"https://api.github.com/users/arggh","html_url":"https://github.com/arggh","followers_url":"https://api.github.com/users/arggh/followers","following_url":"https://api.github.com/users/arggh/following{/other_user}","gists_url":"https://api.github.com/users/arggh/gists{/gist_id}","starred_url":"https://api.github.com/users/arggh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arggh/subscriptions","organizations_url":"https://api.github.com/users/arggh/orgs","repos_url":"https://api.github.com/users/arggh/repos","events_url":"https://api.github.com/users/arggh/events{/privacy}","received_events_url":"https://api.github.com/users/arggh/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":7,"created_at":"2018-11-04T13:54:29Z","updated_at":"2018-11-14T17:03:30Z","closed_at":null,"author_association":"NONE","body":"Currently it seems that this package tries to search for packages in `./packages` folder.\r\n\r\nWould be great, if that was configurable. Some projects consist of multiple Meteor apps that share common local Meteor packages. The folder structure could look like this:\r\n\r\n```\r\n- npm-packages /\r\n    - custom-npm-module1\r\n- meteor-packages /\r\n    - custom-package1\r\n    - custom-package2\r\n- app1\r\n- app2\r\n- app3\r\n```"},"comment":{"url":"https://api.github.com/repos/mattblackdev/meteor-package-intellisense/issues/comments/438738512","html_url":"https://github.com/mattblackdev/meteor-package-intellisense/issues/1#issuecomment-438738512","issue_url":"https://api.github.com/repos/mattblackdev/meteor-package-intellisense/issues/1","id":438738512,"node_id":"MDEyOklzc3VlQ29tbWVudDQzODczODUxMg==","user":{"login":"arggh","id":17210302,"node_id":"MDQ6VXNlcjE3MjEwMzAy","avatar_url":"https://avatars3.githubusercontent.com/u/17210302?v=4","gravatar_id":"","url":"https://api.github.com/users/arggh","html_url":"https://github.com/arggh","followers_url":"https://api.github.com/users/arggh/followers","following_url":"https://api.github.com/users/arggh/following{/other_user}","gists_url":"https://api.github.com/users/arggh/gists{/gist_id}","starred_url":"https://api.github.com/users/arggh/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/arggh/subscriptions","organizations_url":"https://api.github.com/users/arggh/orgs","repos_url":"https://api.github.com/users/arggh/repos","events_url":"https://api.github.com/users/arggh/events{/privacy}","received_events_url":"https://api.github.com/users/arggh/received_events","type":"User","site_admin":false},"created_at":"2018-11-14T17:03:30Z","updated_at":"2018-11-14T17:03:30Z","author_association":"NONE","body":"You're correct, `METEOR_PACKAGE_DIRS` can have multiple paths. I thought I'd share my PoC -branch as a starting point. It currently uses the original local `packages` folder and `METEOR_PACKAGE_DIRS` (splitting the path and including all of them).\r\n\r\n**About overriding:** Do you mean, if we have the same package in two different locations, which one do we use?\r\n\r\nI guess we could rely on Meteor's loading pattern, where the local package in `./packages` always comes first.\r\n\r\nAbout `METEOR_PACKAGE_DIRS` versus _a folder in the extension's configs_... I'm not so sure. Maybe prefer the directory in extension's configuration as a priority, if the default config is empty.\r\n\r\nThen, the developer knows he/she has declared an overriding configuration setting in VS Code. Does that sound reasonable?"}}
{"actor":{"display_login":"arggh"}}