Skip to content

Conversation

lukpueh
Copy link
Member

@lukpueh lukpueh commented Nov 30, 2020

Fixes #1133

Description of the changes being introduced by the pull request:
Add MADR that justifies why we want to add custom classes for complex tuf metadata attributes.

Please verify and check that the pull request fulfills the following
requirements
:

  • The code follows the Code Style Guidelines
  • Tests have been added for the bug fix or new feature
  • Docs have been added for the bug fix or new feature

Add MADR that justifies why we want to add custom classes for
complex tuf metadata attributes.

Signed-off-by: Lukas Puehringer <[email protected]>
@lukpueh lukpueh requested review from sechkova and joshuagl November 30, 2020 14:06
Copy link
Collaborator

@MVrachev MVrachev left a comment

Choose a reason for hiding this comment

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

LGTM

@trishankatdatadog
Copy link
Member

trishankatdatadog commented Nov 30, 2020

💯 💯

In my own experience, it has been extremely useful to decouple the internal, higher-level representation of metadata from the data format themselves. Not only does this let you use different data formats with the same high-level representation, but it also lets you write better code that is independent of the data format (as should be the case).

@lukpueh
Copy link
Member Author

lukpueh commented Dec 1, 2020

Thanks for making a strong case for this proposal, @trishankatdatadog!

@lukpueh lukpueh merged commit d3cd0cd into theupdateframework:develop Dec 1, 2020
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.

Decide on extent of OOP in metadata model
4 participants