Olivier Mélois

Handle dependency import scope

3

I was thinking I'd start implementing a docker plugin, by replicating sbt-native-packager, which uses spotify's docker client. Spotify's docker client depends on `jersey-client`, the [parent](https://search.maven.org/#artifactdetails%7Corg.glassfish.jersey%7Cproject%7C2.22.2%7Cpom) of which contains an "import...

The BSP implementation (which allows editors to talk to mill when the user edits module files) is becoming [first-class-citizen in mill](https://github.com/lihaoyi/mill/pull/969), it'd be interesting to piggyback on ammonite's BSP implementation...

Make dispatcher safer

5

The current Dispatcher suffers from the following problems : * algebraic product components of the effect are lost at the point of dispatch (WriterT's log) * algebraic coproduct components (EitherT,...

Using jvm properties to simplify versioning logic

1

The versioning logic is currently a bit awkward, with the CI creating new branches/committing/pushing on its own for the sole purpose of versioning. A simpler approach would be to use...

Function to format smithy files

6

Hey folks, My team's putting some work into having a polished editor experience : * https://github.com/disneystreaming/smithy-language-server * https://github.com/disneystreaming/vscode-smithy We were wondering whether there was any existing utility function we could...

CORS should support multiple origins

1

The current `cors` trait does not support providing a list of multiple allowed origins. See [https://github.com/awslabs/smithy/blob/main/smithy-model/src/main/java/software/amazon/smithy/model/traits/CorsTrait.java#L37]. This is limiting the implementation of Smithy-driven CORS-related middleware to a strict subset of...

NumberNode's equal definition is impacted by the underlying representation

2

I'm not sure whether this qualifies as a bug, as it's directly coming from what I'd qualify as a java gotcha, but the two nodes values defined below are not...

URI conflict validation is too constraining

7

#### Minimised repro ```kotlin namespace foo service Foo { operations: [Hello1, Hello2] } structure Hello1Input { @httpLabel @required name: String, } @http(method: "GET", uri: "/hello") @readonly operation Hello2 { }...

See https://github.com/VirtuslabRnD/scala-cli/pull/105/checks?check_run_id=3441114875 We may have to protect the logic against this, possibly by checking that the two paths have the same root ?

Paths are not correctly relativised when using bloop

1

Such things get rendered : ` assertion failed (../../../bar/src/test/scala/Foo.scala:13)`