Bug report

Describe the bug
In the config.js addParameters function, if I set isFullscreen: true and open the webpage, it is fullscreen on startup. But if I set isFullscreen: false and open the webpage again, it is still full-screen on startup.

To Reproduce

1. Set isFullscreen: true, open the webpage,
2. Close the webpage or stop the server
3. Set isFullscreen: false, open the webpa

Issue type

I'm submitting a ... (check one with "x")

• [ X] bug report
• feature request
• question about the decisions made in the repository

Issue description

Too wide (and falsy) segregation of GraphQL Types and Resolvers

The first example of this is new ObjectType in src/data/queries/index.js importing fields.
Fields should be taken in context of parent type, not as standalone information.

This can ensure some users that custom types cannot have own field resolvers which is false.

In fact, much of fields which can have own resolvers

Type of issue: (feature suggestion, bug?)

Suggestion

Chapter:

no-chapter

Why use .jsx instead of .js? It's not a best practice: facebook/create-react-app#87 (comment)

https://twitter.com/TheLarkInn/status/1056729742437543936
https://github.com/reactjs/rfcs/blob/gaearon-patch-2/text/0000-lazy.md

Describe the issue / bug.

I added these configs in launch.js,

After F5 debug, already vscode debugging child processes.

but, breakpoint in main process used in folder

Follow up from #4453

Currently, documentation for <b-table> really only discusses and provides examples for the row-selected event:
https://bootstrap-vue.org/docs/components/table/#row-select-support

The only places the row-clicked event is mentioned are:
https://bootstrap-vue.org/docs/components/table/#data-row-accessibility
https://bootstrap-vue.org/docs/components/table/#comp-re

• I've read the guidelines for Contributing to Roots Projects
• This request isn't a duplicate of an existing issue
• I've read the docs and followed them (if applicable)
• This is not a personal support request that should be posted on the [Roots Discourse](https://discourse.roots

We would like to avoid confusion like we have in webpack-contrib/webpack-bundle-analyzer#185

We could document statsFilename and reportFilename options allowing the use of an absolute file path like /path/to/folder so that people would know it's supported.

Let us know in this issue if you would like to contribute to this!