Skip to content
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

Completion attempts get confused by existing yang prefix, and don't use it to qualify candidates #66

Open
davidmichaelkarr opened this issue Jan 11, 2016 · 1 comment

Comments

@davidmichaelkarr
Copy link
Contributor

Completion attempts use the existing symbol prefix to determine candidates.

This needs to treat "prefixes" like "modname:symb" differently. Instead of looking for a symbol that begins with "modname:symb", it needs to look for symbols that begin with "symb" in the module with declared prefix "modname".

@davidmichaelkarr
Copy link
Contributor Author

This can be resolved by changing "YangSimpleCompletionProcessor.getProposalsByMode()" by looking for the colon in the prefix, and determining the module name by passing the prefix before the colon to "module.getImportByPrefix()" and passing that returned module name to "getUsesProposals()" and "getTypeProposals()" (along with adding the second formal parameter to accept this), and then passing that module name to the call to "YangModelManager.search()" in each of those methods. This could also be applicable to other "get*Proposals()" methods, but I have to think about what those mean yet.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant