-
I've had several feedback from users preferring "jest" to "mocha". This issue is open so as to start on discussion on this. If you have used both and prefer one, feel free to give your opinion.
-
I just tryed to play with graphql so I created a new foalts app and followed the instruction on [https://foalts.gitbook.io/docs/topic-guides/api/graphql](https://foalts.gitbook.io/docs/topic-guides/ap…
Edo78 updated
4 years ago
-
Based on my experiences (ymmv):
1. From time to time, I added `controller/entities/services` to its folder, usually by using CLI, but sometimes manually.
Would it be possible to have a command…
-
In this [create-user script](https://foalts.gitbook.io/docs/tutorials/multi-user-to-do-list/3-the-shell-scripts#the-create-user-script), we have conditional checking:
```typescript
await createCon…
-
Since TSLint is being deprecated (https://github.com/palantir/tslint/issues/4534), I think we should start to make this move too, both in the projects and also in the cli generated code. I have some c…
-
# Issue
FoalTS uses [morgan](https://www.npmjs.com/package/morgan) under the hood to log HTTP requests. We may want to disable this global logger in certain situations:
- when running E2E tests
…
-
Creation of a new FoalTS project using `foal create app app` does not successfully complete. I run into the following error:
```cmd
📂 Creating files...
📦 Installing the dependencies...
yarn …
-
# Issue
We already have a command (`foal g vscode-config`) to start a Foal application with the debugger. But using the debugger can also be very useful during unit or acceptance testing.
# Solu…
-
Are root import supported? I.e. instead of:
`import { Foo } from "../../../entities"`
you could do:
`import { Foo } from "@/entities"`.
-
npm run develop
> foalts@0.0.0 develop /Users/rick/Documents/projects/foalts
> npm run build:app && concurrently "npm run build:app:w" "npm run start:w"
> foalts@0.0.0 build:app /Users/rick/D…