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
A useful feature might be having a variable that contains the different options for each parameter. This both lets users know which options are available for each parameter (without having to look up the docs each time) and only have to type the first couple letters before hitting tab to complete the rest of the option.
The variable could be automatically constructed from the engine default priorities as soon as the the engine is created. ie the create_engine_opts function would be called internal to monarch_engine.
That said, we'd need to add some more info about options for predicates.
create_engine_opts<-function(engine){
## Not shown: simplify names from "category_priority" to "categories" to match args in `expand`opts<<- lapply(engine$preferences, function(x){ x|>`names<-`(gsub("biolink:","", x))|>as.list() })
}
monarch<- monarch_engine()
This would let users construct their queries like this:
A useful feature might be having a variable that contains the different options for each parameter. This both lets users know which options are available for each parameter (without having to look up the docs each time) and only have to type the first couple letters before hitting tab to complete the rest of the option.
For example, currently we have:
The variable could be automatically constructed from the engine default priorities as soon as the the engine is created. ie the
create_engine_opts
function would be called internal tomonarch_engine
.That said, we'd need to add some more info about options for predicates.
This would let users construct their queries like this:
The text was updated successfully, but these errors were encountered: