Skip to content

Commit

Permalink
Update README.md
Browse files Browse the repository at this point in the history
  • Loading branch information
dcarroll committed Apr 20, 2016
1 parent 11d3de0 commit e5247a9
Showing 1 changed file with 1 addition and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -17,7 +17,7 @@ Once you have both of these installed, create a new folder to be your working fo

Launch Sublime Text and open the new folder. If you have not logged in recently from the command line, you can right-click the folder in Sublime's sidebar and click "Salesforce Login". In the bottom tray of Sublime enter your username and hit the enter key, enter your password (the password will be shown in clear text, sorry) and hit the enter key.

Note: If you receive the error message, "Sublime Lightning Plugin requires the Force.com CLI to function.." and you are certain that the CLI is in your path and is marked as executable, you can try in stalling the the [Fix Mac Path plugin](https://github.com/int3h/SublimeFixMacPath) which may solve the issue.
Note: If you receive the error message, "Sublime Lightning Plugin requires the Force.com CLI to function.." and you are certain that the CLI is in your path and is marked as executable, you can try in stalling the [Fix Mac Path plugin](https://github.com/int3h/SublimeFixMacPath) which may solve the issue.

At this point, you will not be able to create any Lightning artifacts, unless you have a folder under your work directory named 'metadata/aura'. You can, however, fetch existing Lightning artifacts by right clicking the work folder and selecting "Fetch Lightning". This will query your Salesforce instance for all Lightning bundles and display them for you to choose which thing you want to edit. You can open all lightning bundles at once, scroll to the one you want, or begin typing the name of the Lightning bundle to filter the list and then select the one you want.

Expand Down

0 comments on commit e5247a9

Please sign in to comment.