Skip to content

[Idea] Storage Layer abstraction #11

@Spedge

Description

@Spedge

So, after working on this for quite a while, I'm starting to see where I've got to be far more strict around the abstraction of concepts if we are going to make this solution viable for more than just me as a user ;)

The first challenge I intend to tackle is the storage layer. As I wrote it at first, it ended up very Java-centric and leant on some of the concepts around Group, Artifact and Version (GAV). This didn't work as I started to play with Python and although I implemented a concept of translation, it didn't quite sit in my head as a simple solution to what is, generally, a solved problem.

So - back to basics. Below is what I intend to start implementing in a new branch - let's see how it goes.

storageredesign

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions