tacitknowledge/autopatch — comment on commit 9e3b65077c527d846395cd27464f227877407740
File:  line 0
By MexicanHacker:

Hey Ulises,

I would like to work in another solution for this as oppose to extend the PatchInfo interface, maybe roll back for the time being. The reasons are this:

1. PatchInfoStore having read/write functions it's fine due the fact that only developers will handle that
2. By extending the interface we are forcing the future interfaces to use all the methods and we should aim for a solution that favors composition over inheritance in this case.
3. I think having only once interface (implementation) it's clearer for our purposes at this point, we can achieve the same goal by adding an object to modify the table and protect it from being accessed for outside classes (see point two about favoring composition)

Let me now what do you think