TISTUD-6674:Content Assist: Documentation link in Content assist opens invalid URL

[sujmishra]

1. Created a new extension of the com.aptana.editor.common.textHover in titanium UI to handle titanium
   specific URIs
2. Handled titanium specific URIs in a subclass
3. Added new test for the same.

[build]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
http://studio-jenkins.appcelerator.org//job/studio3-prs/106/Test PASSed.

[sgtcoolguy]

I'd prefer we not make references to titanium project natures in studio3 codebase. Isn't there a mechanism for matching enablement expression based on how specific the variable used is (like command handlers do)? I recall Eclipse having infrastructure for that, so in this impl you'd just say always enabled and not reference any vars.

[build]

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
http://studio-jenkins.appcelerator.org//job/studio3-prs/107/Test PASSed.

[sgtcoolguy]

Why was this merged?
Perhaps I should have been more explicit in my feedback. Beyond removing the enablement details from pointing at the titanium nature constants, the other main issue is that the extension point has no concept of the enablement expressions. You need to add the support for that into the consumer of the textHovers.

[sujmishra]

We do have enablement expressions on the extension point.