Skip to content

Evaluate our current design patterns #114

Description

@hesspnnl

Evaluate the current design of NMDCMetadataGenerator and NMDCWorkflowMetadataGenerator classes.

  • Create better rules for hwne a funciton should go in one vs the other.
  • Does the name NMDCWorkflowMetadataGenerator make sense with the new addition of material processing steps? What name could be better used and encapsulate more changes without the need for alterations in the future?
  • Do we need the use of self.attribute name in fucntions in these class? I feel they add confusion adn should be passed in as parameters.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Fields

No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions