Open ghost opened 10 years ago
+1
I have tried both ways of installing the plugin and when adding it as a repository the appropriate folder is created. I believe the issue is caused due to the different name that is provided in the package control.
You can take a look at the listing in the package control channel .
{
"name": "Jira",
"details": "https://github.com/mix86/SublimeJira",
"labels": [
"atlassian jira",
"jira integration",
"jira"
],
"releases": [
{
"sublime_text": ">=3000",
"details": "https://github.com/mix86/SublimeJira/tags"
}
]
}
The current name is Jira but the configuration in menu points to SublimeJira. I dont know if this affects also the conf. I have created a fix in package control channel and a fix in SublimeJira.
@mix86 should decide which one he would like to keep. If we keep the fix in SublimeJira the path of settings will be ${packages}/Jira/SublimeJira.sublime-settings. If we keep the fix of package control the package will remain as is just that the listing will be moved to s.json and we will remove the name 'Jira'.
I believe that the fix should be the one of the package control channel since Sublime allows installing a package from a repository and this will create other issues to devs that will choose the manual way of installing.
After installation, I wanted to view the default settings. The file opened empty and I couldn't save it, too. The file path was ... sublime3\Data\Packages\SublimeJira\SublimeJira.sublime-settings The folder created on my drive is called "Jira" instead.
As I couldn't find the source of the issue I guess it's a mistake in the description for the package manager?!
Best regards