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

Type-check consent codes #14

Open
mcupak opened this issue Apr 9, 2018 · 0 comments
Open

Type-check consent codes #14

mcupak opened this issue Apr 9, 2018 · 0 comments

Comments

@mcupak
Copy link
Contributor

mcupak commented Apr 9, 2018

With OAS 3.0, we should be able to handle consent codes better by utilizing inheritance. I imagine we'd have classes containing enums for primary, secondary categories and requirements + a qualifier field for variable codes.

The hierarchy could probably be something like this:

  • DataUseCondition
  • QualifiedDataUseCondition -> DataUseCondition
  • PrimaryDataUseCondition -> DataUseCondition
  • SecondaryDataUseCondition -> DataUseCondition
  • RequirementDataUseCondition -> DataUseCondition
  • QualifiedPrimaryDataUseCondition -> QualifiedDataUseCondition
  • QualifiedSecondaryDataUseCondition -> QualifiedDataUseCondition
  • QualifiedRequirementDataUseCondition -> QualifiedDataUseCondition

We need to check how this behaves practically with codegen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant