Øyvind Raddum Berg
Øyvind Raddum Berg
I've been doing some scalajs hacking lately, and had a look at autowire the other day. I exported a trait with an accessor method (no parameters), and that made my...
- add `TestRun` and `TestRuns` structures to aggregate all produced `TestSuiteEvent.Results`. - propagate all test results back up to service - use test results to return `bsp.StatusCode.Error` on failed tests...
Extending `TestResult#data` with structured summary would be nice indeed. Can you create an issue and add todo for that? _Originally posted by @kpodsiad in https://github.com/scalacenter/bloop/pull/1769#discussion_r934367560_
I just upgraded to 1.4.0-RC2 and got these warnings: ``` [info] set current project to slinkydemos (in build file:/home/olvind/scalablytyped/slinkyDemos/) [warn] there are 26 keys that are not used by any...
Don't use phases for files within a library. this is preliminary work for improving javascript modules
So far we've been pretty pedantic in the handling of things like re-exported types. ```typescript declare module "libfoo/impl/foo" { export class Foo {} } declare module "libfoo" { export import...
https://webpack.js.org/guides/package-exports/ this is required to support newest version of firebase, and probably other libraries with peculiar layouts. This will be done after the cleanups in #366 , and will come...
There is rudimentary support for: - augmented modules. Barely enough to make lodash work, while being pretty wrong for everything else. Needs a complete rewrite - augmented namespaces is supported...
This is rather clunky, but has been necessary in some cases for both scalac and intellij to behave. intellij might still be the limiting factor for scala 3
There were a bunch of reasons why the current encoding with sealed trait strings were chosen, and it's time to revisit and see if those reasons still hold with scala...