Visualize hierarchical estimates
Go to file
2021-09-22 22:59:06 +02:00
lib Removed mongo integration 2021-09-22 22:59:06 +02:00
pages Removed mongo integration 2021-09-22 22:59:06 +02:00
public MVP with just an ordering, but no quantitative estimates 2021-06-06 23:14:05 +02:00
styles Changed slider order. Inferred relative utility compared to a reference point. However, object structures used in the code remain messy 2021-06-10 21:59:48 +02:00
.gitignore chore: Save before npm audit fix 2021-09-22 22:24:31 +02:00
package-lock.json Removed mongo integration 2021-09-22 22:59:06 +02:00
package.json Removed mongo integration 2021-09-22 22:59:06 +02:00
postcss.config.js MVP with just an ordering, but no quantitative estimates 2021-06-06 23:14:05 +02:00
README.md Changed slider order. Inferred relative utility compared to a reference point. However, object structures used in the code remain messy 2021-06-10 21:59:48 +02:00
tailwind.config.js MVP with just an ordering, but no quantitative estimates 2021-06-06 23:14:05 +02:00

Object structure

The core structure is json array of objects. Only the "name" attribute is necessary; the id is also internally necessary but it's created on the fly if it doesn't exist. The reason that ids are needed is that comparing objects is annoying.

[
    {
        "id": 1,
        "name": "Peter Parker",
        "someOptionalKey": "...",
        "anotherMoreOptionalKey": "..."
    },
    {
        "id": 2,
        "name": "Spiderman",
        "someOptionalKey": "...",
        "anotherMoreOptionalKey": "..."
    }
]