For backward compatibility (for users used to getting character vectors of nodes out of tools like getDependencies and then doing their own manipulation) we discussed having an option to indicate to such tools to return character vectors rather than compact representations (often (usually/always?) varRanges).
As far as inputs to various tools, I think most of them already take either varRanges or character vectors.
I believe essentially all the tooling is in place to go back and forth between varRanges (and presumably nodeRanges) and character vectors. If not, I think that will become quickly obvious in carrying out this task.
For backward compatibility (for users used to getting character vectors of nodes out of tools like
getDependenciesand then doing their own manipulation) we discussed having an option to indicate to such tools to return character vectors rather than compact representations (often (usually/always?) varRanges).As far as inputs to various tools, I think most of them already take either varRanges or character vectors.
I believe essentially all the tooling is in place to go back and forth between varRanges (and presumably nodeRanges) and character vectors. If not, I think that will become quickly obvious in carrying out this task.