Skip to content

feat: support mixed residue types - #50

Merged
fubin1999 merged 2 commits into
mainfrom
mixed-type
Aug 15, 2026
Merged

feat: support mixed residue types#50
fubin1999 merged 2 commits into
mainfrom
mixed-type

Conversation

@fubin1999

Copy link
Copy Markdown
Member

Summary

  • preserve generic and concrete residues within individual parsed glycans and across result vectors
  • remove the unreleased drop_generic argument and filtering path from all parsers
  • add cross-format regression coverage for GlyTouCan G00051UX and refresh generated documentation

This aligns glyparse with glycoverse/glyrepr#90.

Verification

  • devtools::test() — 1,658 expectations passed
  • pkgdown::check_pkgdown() — passed
  • devtools::check(document = FALSE) — 0 errors, 0 warnings, 1 environment-only clock note
  • revalidated 4,383 historical mixed-type corpus cases
  • parsed all 20,082 IUPAC-Extended corpus entries: 20,061 concrete, 3 generic, and 18 mixed

Preserve generic and concrete residues in the same parsed graph and result vector. Remove the unreleased drop_generic argument, refresh documentation, and add cross-format regression coverage.
@codacy-production

Copy link
Copy Markdown

Up to standards ✅

🟢 Issues 0 issues

Results:
0 new issues

View in Codacy

NEW Get contextual insights on your PRs based on Codacy's metrics, along with PR and Jira context, without leaving GitHub. Enable AI reviewer
TIP This summary will be updated as you push new changes.

@fubin1999
fubin1999 marked this pull request as ready for review August 15, 2026 09:29
@fubin1999

Copy link
Copy Markdown
Member Author

@codex review

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 576047be0b

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread NEWS.md
* Parsers now preserve unusual monosaccharide configurations using `glyrepr` names such as `D-Fuc`, `L-Gul`, and `D-Fucf`, while unprefixed names retain their natural configurations. (#43, #44)
* Parsers now preserve explicit furanose forms as `glyrepr` monosaccharide names such as `Galf`, `GlcfNAc`, and `Neuf5Ac` across IUPAC, GlyCAM IUPAC, GlycoCT, WURCS, LINUCS, Linear Code, and KCF inputs. (#41)
* `auto_parse()` and all format-specific parsers gain `drop_generic` to replace generic glycans with `NA` when generic and concrete glycans coexist, with a message reporting the number dropped. (#39)
* `auto_parse()` and all format-specific parsers now preserve generic and concrete residues mixed within a glycan and across parsed vectors. (#50)

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Require the glyrepr revision that supports mixed types

When this package is installed with a pre-glyrepr#90 glyrepr 0.14.0.9000 snapshot, that dependency still satisfies the unchanged Imports requirement even though its constructors reject mixed monosaccharide types. Consequently, the newly advertised mixed inputs continue to error in both wrapper paths. Bump glyrepr's development version and require that version here, or pin a compatible remote revision.

Useful? React with 👍 / 👎.

@fubin1999
fubin1999 merged commit 6b4448c into main Aug 15, 2026
13 checks passed
@fubin1999
fubin1999 deleted the mixed-type branch August 15, 2026 09:35
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant