Discard MetaForgeParser superclass and use the Spike parser superclass instead.

Open
#91 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
4/5
Estimated time
3-5 days
Newbie friendliness
25/100
Issue type
Refactor
Clarity
Needs clarification
Activity status
Stale
Tech stack
python
Domain
backend

Research direction

No files or tests are named. First locate MetaForge's parser superclass and determine how Spike exposes its replacement, then compare the interfaces used by existing parsers. Done means MetaForge parsers use the Spike superclass and remain compatible with Spike metadata parsing and HyperThought uploads.

Written by the indexing model from the issue text.

Description

Spike is a new application that the HyperThought team is using to be able to parse metadata and upload to HyperThought. Mike and I thought that maybe we should use their superclass for our parsers instead so that any parsers we make for MetaForge are also compatible with Spike.

Dominant language
Python
Stars
2
Forks
4
No merged PRs in 30d

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from BlueQuartzSoftware/MetaForge

All issues in BlueQuartzSoftware/MetaForge

Similar issues

More Python issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.