Import Functionality, Major Version Bump, and More!
This weekend held one of the most significant sprints since the beginning of the project. The biggest feature push was the import functionality. As of v1.1.0, users can import service assignments, tools, and the aggregate history from CheckM8. This being aggressively use-case specific, I plan to implement a vendor-neutral option that involves downloading a template csv, adding data it matching the containstraints, and uploading the now-populated csv. This will be simpler as far as TK is concerned, but more work for the end-user.
To summarize the sprint:
- 30 commits on friday
- designing the import flow
- 26 commits on saturday
- JS Promises aren’t async/await
- 18 commits on sunday
- I promise I don’t understand promises
- 8 commits on monday
- This was a holiday, and was mostly linting and refactoring.
All this being said, there is a TON of documentation that needs to be updated. That might be the goal of the next sprint:
- Flush the database
- register the first/admin user
- import data following the CheckM8 workflow
and document as we go, exclusively how things are at that time. Afterwards, I can go back through and side-by-side opine how things ideally should be. This would give an accurate picture of what needs doing to get from where we are to where I want to be.
Below are some photos of ToolKeeper with filled in data. All of this is legacy data, and I’ve approved it with the customer before posting it here. It’s incredibly satisfying to finally have something tangible to show for 6mo of development and design.
