Unclear docs re debug mode
See original GitHub issueThe docs currently show re debugging:
If you pass {debug: true} as one of the options in your initialize settings
It is unclear what is meant by initialize settings, and I couldn’t find reference to them nor their mention anywhere.
The changelog states that it can be passed to any Sync
query, which is not clarifying, and the codebase mentions show only the Sync
function takes the debug
option
I would put a PR in if I had a clue how to enable debug
Issue Analytics
- State:
- Created 5 years ago
- Comments:5 (4 by maintainers)
Top Results From Across the Web
Documentation about --no-debug mode unclear (#153) · Issues
This may cause confusion when --no-debug mode is activated and all output goes to /dev/null without any mention in journal.
Read more >Enabling debug logging - GitHub Docs
To enable runner diagnostic logging, set the following secret in the repository that contains the workflow: ACTIONS_RUNNER_DEBUG to true . To download runner ......
Read more >Working in the Inspector - Unity - Manual
To turn on Debug mode, click the More Items (⋮) button to open the context menu, and select Debug. To return to Normal...
Read more >What does Lightning Debug Mode do exactly?
The answer is: I misunderstood the docs plain and simply. Optimization and minification are performed on framework code only.
Read more >Debugging methods and error types - HubSpot Developers
You can enable debug mode on a live page by loading the page with a ?hsDebug=true query string in the URL. Please note ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Here’s another hack btw.
Bookshelf does a shallow copy of options on use (even down the eager chain). So if you pass an options object with a preset namespace (e.g. context, or scope) you can retain the full qb. This allows for some hacking.
Edit; It’s late and this was of the top of my head but let me know if you want a more succinct example.
I don’t know. But debugging my latest issue (https://github.com/bookshelf/bookshelf/issues/1823) would have been easier if I could have seen a log of mutations or functions performed on models. Knex doesn’t show Bookshelf models ids, and logging yourself presumes you know what you’re looking for.