Skip to content
This repository was archived by the owner on Oct 4, 2022. It is now read-only.
This repository was archived by the owner on Oct 4, 2022. It is now read-only.

Namespace Issues #365

@Brennan1994

Description

@Brennan1994

Throughout model we have horrible and inconsistent namespaces. Best practices here: https://learn.microsoft.com/en-us/dotnet/standard/design-guidelines/names-of-namespaces

This is becoming an issue when trying to reference things in Model from veiwmodel. Nothing is prefixed with anything that indicates it's coming from fda-model. To access Inventory.cs, for example, you'd assume based on folder structure the path would be something like HEC.FDA.Model.structures.Inventory, the reality is the correct path is just structures.Inventory.

So far this is just annoying, but could potentially cause conflicts when path names start becoming non-unique. This ought to be fixed at some point, and the issue grows the longer we let it sit, because going through and fixing these namespaces is going to change the method signatures of EVERYTHING we reference in the view.

Metadata

Metadata

Assignees

Labels

invalidThis doesn't seem right

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions