You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Sep 24, 2019. It is now read-only.
The built-in auto-completion in the BELMgr was tested with following examples:
rxn => delivers reaction method and several other EGID entries => Works
rxn(r => delivers all methods and the RGD namespace => not working
a => delivers abundance, complexAbundance and some other methods. By choosing complexAbundance, the BELMgr outputs complex() and the cursor jumps to the end position. Apparently, the caret position is not being considered. => not working
Using the BEL 2.0 endpoint. Also the API is returning the results very slow.
The text was updated successfully, but these errors were encountered:
For completing on namespace values, it will not respond with less than 3 characters.
The ordering of the completions is up to the client.
Tony - can you provide more detail on when it will provide semantically valid results vs not or more examples with more of a description of the results?
Regarding the BELMgr caret position, this is a known issue (OpenBEL/belmgr#85) and not planned to be fixed in this milestone. The API is providing the correct caret position.
In the BELMgr - we don't kill requests to the autocomplete service due to an issue with how we handle promises. This causes extra latency in the BELMgr autocompletes. It's also a complex autocomplete and has been optimized significantly already, but we agree that it is still not fast enough. More optimizations, however, are out of scope for the BELIEF milestone.
The built-in auto-completion in the BELMgr was tested with following examples:
rxn
=> delivers reaction method and several other EGID entries => Worksrxn(r
=> delivers all methods and the RGD namespace => not workinga
=> delivers abundance, complexAbundance and some other methods. By choosing complexAbundance, the BELMgr outputs complex() and the cursor jumps to the end position. Apparently, the caret position is not being considered. => not workingUsing the BEL 2.0 endpoint. Also the API is returning the results very slow.
The text was updated successfully, but these errors were encountered: