Skip to content

Commit 840e95e

Browse files
Add known issue about using a build.yaml (#317)
Closes #268
1 parent 5b89d2e commit 840e95e

File tree

1 file changed

+23
-0
lines changed

1 file changed

+23
-0
lines changed

README.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -367,6 +367,29 @@ Please file [FlutterGen] specific issues, bugs, or feature requests in our [issu
367367

368368
Plugin issues that are not specific to [FlutterGen] can be filed in the [Flutter issue tracker](https://github.com/flutter/flutter/issues/new).
369369

370+
### Known Issues
371+
#### Bad State: No Element when using build_runner
372+
If you get an error message like this:
373+
```
374+
[SEVERE] flutter_gen_runner:flutter_gen_runner on $package$:
375+
376+
Bad state: No element
377+
[SEVERE] Failed after 16.0s
378+
```
379+
380+
The you most likely have a customized `build.yaml` to configure the build runner. In that case, all you have to do is to add the `pubspec.yaml` as build source to your `build.yaml`
381+
382+
```yaml
383+
targets:
384+
$default:
385+
sources:
386+
include:
387+
- pubspec.yaml # add this line
388+
- ...
389+
```
390+
391+
See #268 for the corresponding issue discussion.
392+
370393
## Contributing
371394

372395
**We are looking for co-developers.**

0 commit comments

Comments
 (0)