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

[BUG] Obo.parseOboTerms too strict about parsing whitespace #118

Open
Freymaurer opened this issue May 12, 2021 · 0 comments
Open

[BUG] Obo.parseOboTerms too strict about parsing whitespace #118

Freymaurer opened this issue May 12, 2021 · 0 comments
Labels

Comments

@Freymaurer
Copy link
Member

Describe the bug
I tried to parse the nfdi4pso.obo file and got no oboterms. Found out, that whitespace after [Term] kill the parsing, so i added a Trim function. Maybe this could be added to the core function?

To Reproduce
Steps to reproduce the behavior:

  1. Download .obo file from above or use the following:
"""
[Term] 
id: NFDI4PSO:0000005
name: Humidity Day
def: "This term defines the relative humidity of the air at daytime, it is a specialised concept of http://www.ontobee.org/ontology/PECO?iri=http://purl.obolibrary.org/obo/PECO_0007197”
comment: “”
"""
  1. Use code to parse:
termString
|> String.split('\n')
|> Seq.map (fun x -> x.Trim()) // Without this it will not work
|> Obo.parseOboTerms
|> Array.ofSeq

Additional context
@kMutagene found that this could be added here via en.Current -> en.Current.Trim().

@Freymaurer Freymaurer added the bug label May 12, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant