We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The MafOutputRenderer changed how some funcotation fields are accessed.
MafOutputRenderer
Need to make VCF output consistent with the code in MAF output, and need to make sure it's consistent to the VCF format.
Specifically, VCFOutputRenderer should use the funcotation map that is now created internally to go through and render the annotations.
VCFOutputRenderer
Specifically use Funcotation::getFieldNames and Funcotation::getField.
Funcotation::getFieldNames
Funcotation::getField
The text was updated successfully, but these errors were encountered:
I think this is already done as part of #4872 ... @jonn-smith Can you confirm?
Sorry, something went wrong.
@LeeTL1220 actually I think this was actually addressed in #4838.
Either way, I think we can close this one.
LeeTL1220
No branches or pull requests
The
MafOutputRenderer
changed how some funcotation fields are accessed.Need to make VCF output consistent with the code in MAF output, and need to make sure it's consistent to the VCF format.
Specifically,
VCFOutputRenderer
should use the funcotation map that is now created internally to go through and render the annotations.Specifically use
Funcotation::getFieldNames
andFuncotation::getField
.The text was updated successfully, but these errors were encountered: