-
Notifications
You must be signed in to change notification settings - Fork 23
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
Go to declaration across modules #80
Comments
Hi, will take a look at it. Thanks! |
Hi, thanks and sorry for the delay getting back to you. Should "go to declaration" work across files? Maybe I don't have something setup right. Create a library module xquery version "3.0";
module namespace lib = "lib";
declare variable $foo := "foo";
declare function bar() as xs:string { "bar" }; and a main module xquery version "3.0";
import module namespace lib="lib" at "lib.xq";
$lib:foo,
lib:bar() The auto-complete works fine - typing I'm using 0.0.9 btw. Thanks again |
Hi, No worries. As I thought the issue is not really related to the multi-module setup but the fact that marklogic has a bit more relaxed rules around variable declaration. If in your library module you'll add prefix in your variable declaration then it'll start working fine. Anyway... I'll try making resolution more relaxed as I think that most of marklogic xquery code uses this "feature" of not having to add prefix in variable declaration. |
After some reading... It's probably a hidden feature nowhere described similar to defaulting function namespace for library modules to module namespace (http://docs.marklogic.com/guide/xquery/enhanced#id_20838). |
ah I see, thanks for looking into it. I didn't realise it was a MarkLogic thing to default variables and functions to the library namespace - I write all my code like that :) |
Will require selecting xquery "flavour" (creating a facet) for solving. Will go with next release. |
Set in [File | Settings | Project settings | XQuery | Other | XQuery flavour] value MarkLogic and should work fine now. |
Auto-complete correctly suggests variables and functions from imported modules, but the go to declaration feature doesn't work, it just says "Cannot find declaration to go to".
The text was updated successfully, but these errors were encountered: