Mara Schulke

## Current State As of right now buffrs users can only pin their dependencies which yields to a limited flexibility when using, especially in a fast moving environment. ## Implementation...

## Current State At the moment users specify _registries and repositories_ in every single dependency declaration. This does not only lead to a chunky `Proto.toml` as we repeat common information...

Usages of `PackageName::unchecked` / How should errors look to users if we dont have a package name to display?

4

Having this means we can violate "type safety". Are there multiple places where we are using this? I think I only saw one use of it, where we do: `PackageName::unchecked(".")`....

Enable users to add the latest version of a dependency through `buffrs add`

1

It would be greatly improving the user experience to be able to add a dependency using `latest` instead of a fixed version string and having buffrs figure out what the...

Installing updated packages using `buffrs install` fails when a package is already locked to a prior version

1

Reproduce: Given a project `foo` that depends on `bar@=0.1.0`: 1. Run `buffrs install` which install `[email protected]` and creates a `Proto.lock` 2. Edit the manifest to e.g. depend on `bar@=0.2.0` 3....

Improve and stabilize the protobuf validation

2

cc @xfbs We need to roll out more linting rules and restructure the validation implementation eventually. @xfbs could you guide tom on this?

Enable more clippy lints for automated code review

1

https://rust-lang.github.io/rust-clippy/master/index.html#/import?groups=cargo,complexity,correctness,deprecated,nursery,pedantic,perf,restriction,style,suspicious