Patrick Elsen

Implement `get_mut()` for map types

1

Implement `get_mut()` API for `RangeMap` and `RangeInclusiveMap`, to mutate values.

Don't panic on empty ranges.

14

Currently, on insertion there are assertions to check for invalid ranges: ```rust // RangeMap::insert assert!(range.start < range.end); ``` ```rust // RangeInclusiveMap::insert assert!( range.start() = end` (or `start > end` for...

Implement `entry()` API more control when inserting values.

Implement `iter_mut()` API for `RangeMap` and `RangeInclusiveMap`, to mutate values on iteration.

Credentials storage does not respect the XDG specification

2

Currently, the credentials are stored in a hard-coded path determined by the `$BUFFRS_HOME` variable, or in `~/.buffrs/credentials.toml`, see [this code](https://github.com/helsing-ai/buffrs/blob/main/src/credentials.rs#L35C9-L35C9). While this is initially a sensible approach, there are some...

Buffrs library pulls in a lot of dependencies that are not needed.

4

`buffrs` is two things at once - a library which is used to build things, using `buffrs::include!()` - a binary which is used to setup and manage buffrs projects The...

> I still think that the "proto_path" is not related to the store, so: > > proto/* -> the current package > proto/vendor/* -> the "package store" > > So...

The `PackageStore` has only one responsibility: that is storing packages. As such, it "owns" the data inside `proto/vendor`. It should not really be responsible for releasing packages. For that reason,...

Look into the error handling discussions and see if it is really necessary to return `miette::Result` from low-level implementations (such as `FromStr`) and methods. My general feeling is that this...

This issue tracks the progress of implementing a first rough draft of the registry. The goal for this is to be something that can be run locally.