Documentation Feedback
See original GitHub issuePlease use this issue to give feedback on the documentation published at: https://fragmuffin.github.io/cqparts/doc/
Note: this documentation isn’t always updated with changes to master
; it often lags a little behind.
This issue will be closed upon the release of v0.2
regardless of the state of documentation.
Issue Analytics
- State:
- Created 6 years ago
- Comments:12 (8 by maintainers)
Top Results From Across the Web
Get feedback on your documentation • Freddy Feedback
Documentation feedback. It's difficult to improve your documentation if you don't know what your users think about it. Did they understand the info?...
Read more >IBM Documentation Feedback
Your comments are sent directly to the authors to help improve IBM product information. To report a defect through IBM Software Support, go...
Read more >Documentation feedback - Texas Instruments
Notice: This form is for reporting errors or providing comments about a technical document. If you are seeking support or asking a question,...
Read more >How To (Actually) Manage And Document Feedback - Upvoty
Managing customer feedback can be tricky. Unstructured feedback leads to data fragmentation and teams working in silos. Here's how to manage.
Read more >How To Get User Feedback On Documentation Using ...
5 Effective Ways To Collect User Feedback On Your Documentation · Enable Customer Comments On Documentation · Collect Emojis Feedback On ...
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
@jmwright I’ve made this topic for general doc feedback, based on your comment in #28
Good catch on the constraints code! I’ve fixed it up for now (commit: 6059f10), but so much of the base code is in flux right now. That code is in a
doctest
block, so future changes should cause test failures… and quite frankly, it causes an error now, because I haven’t put theComponent.build()
method in 😉Thanks @dcowden ! I’ll put this into #30