Alexis Hernandez
Alexis Hernandez
Right now, the app returns either 200 or 500 for all responses, it would be ideal to switch to proper http status codes like 401, 404, 400, etc.
The [index.html](https://github.com/wiringbits/scala-webapp-template/blob/master/admin/src/main/js/index.html#L23) has a hardcoded script name for loading the js bundle, it would be nice to avoid this and use webpack or sbt to place the actual script name...
Upgrading has some tricky details (https://www.scala-js.org/news/2022/04/04/announcing-scalajs-1.10.0/) because we need to use the secure random library for running the app but the insecure one for tests, this occurs because the test...
The task can be either done completely or by the frontend/backend separately. Let's add the necessary fields to filter users by id, name, or email. Frontend: - Responsive view. Backend:...
It would be useful to be able to override the `application.home` property in the [logback.xml](https://github.com/wiringbits/scala-webapp-template/blob/master/server/src/main/resources/logback.xml#L8) settings, let's find a way to do so, and propagate it to the start [script](https://github.com/wiringbits/scala-webapp-template/blob/master/infra/config/server/server.service.j2#L12)....
There is a minor TODO note that has been in the project for a year now, it should be trivial to fix it: https://github.com/AlexITC/chrome-scalajs-template/blob/master/src/main/scala/com/alexitc/chromeapp/background/services/storage/StorageService.scala#L26
For any sane project, tests are mandatory, which gets a bit tricky in Scala.js browser extensions, let's add examples so that our users do not need to figure everything by...
Preferably, there would be a template or simple project that let's you fill some holes to get it working.
### How it works At the moment, an error is rendered like this: ``` { "type": "field-validation-error", "message": "An error message", "field": "email" } ``` The fields have the following...