I think it is worth mentioning that the solution stated Catching unresolved and rejected promises is not always valid. what I mean is that if a promise is caught on a later turn of the Node.js event loop, then probably throwing an error on this global catch is not a good idea. I am wondering how this is counted as best practice while obviously from the node official documentation it should

It says there is good resources and the first title on the landing page says that those practices are bad and should not be used any more. Maybe find something else to link to make that point?

As the screenshot I have added point out, the whole of the content uses a declarative and instructive verbiage while explaining concepts whereas a few of the headings in the Coding Style sections deviate from the rest in a way t

The double dollar assertion: https://github.com/GoogleChrome/lighthouse/blob/e87a8b76e66208be0266c6e3a3b648dbebe79521/lighthouse-core/scripts/i18n/collect-strings.js#L344

Is a bit aggressive, it should check for basic $$ but allow $ICU_0$$ICU_1$. This should be validated with regex like \$([^$]*?)\$ and asserting that each capture group isn't empty instead of a more basic \$\$.

• Suggestion: Less strongly advocate for ContentProviders in situations where their complexity does not reward the effort.
• Best practices for SQLite usage?
• Possibly mention Realm/Room depending on our experiences.

When you're viewing a cheatsheet on the https://cheatsheetseries.owasp.org website it isn't immediately obvious that the content is pulled from GitHub, or how you could contribute to the project on the cheatsheets themselves (although there is a note at the bottom of the homepage).

Making this more obvious in the sheets themselves will encourage people to contribute (or at least raise issues).

Page Affected: https://developers.google.com/web/updates/2020/01/devtools

What needs to be done?
Call (Ctrl+P) Print dialog and save page as PDF
Actually:
Call (Ctrl+P) Print dialog. Dialog somehow closes himself and deny access to print page at all.

User agents:
Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/78.0.3904.108 Safari/537.36 OP

From reading about do expressions, it seems that the code section under the text

With an appropiate transpiler you can take advantage of the upcoming do expression which is currently on stage-1

should be do { instead of do => { on line 5, but I'm not 100% sure. Can someone please clarify?

It will be better if you provide an example with MVC and MVVM or other Patterns.
Examples are more valuable to understand the context

If you're creating a bug/problem report, please include followings:

• Your Abp package version. - 5.2
• Your base framework: .Net Core. 3.1

Aspnetboilerplate Angular Template 5.2

Integration with the explanation from the page:
https://aspnetboilerplate.com/Pages/Documents/OData-AspNetCore-Integration

in .net core 3.1 mvc.internal is removed:

Could not load type 'Microsoft.AspN

Expanding on #21, we should make a distinction for exported and unexported types, and call out advice to avoid bleeding implementation details through APIs when embedding.

cc @abhinav @prashantv

https://opensource.guide/legal/

It is not clear to me how i should practically note the copyright of a code part (for example 5 lines from a MIT project). Is it legally OK to just note the source, author and license in the commit message description or should it be in the header of the file or in the LICENSE file of the project?

When i copy whole files, the license header should not be r

i have been using this for a while as i find it a convenient way to tweak eslint settings via eslint conventions, and i just noticed that it wasn't mentioned in the documentation.

should this be documented o

Description

Add a ReadMe file in the GitHub folder.
Explain usage of the Templates

Other Comments

Principles of NLP Documentation
Each landing page at the folder level should have a ReadMe which explains -
○ Summary of what this folder offers.
○ Why and how it benefits users
○ As applicable - Documentation of using it, brief description etc
Scenarios folder:
○

🐛 Bug report

Description

When I run a scan against a very long URL, word wrap breaks in the results.

Environment

• webhint version: 1.2.1
• Browser version: Edge Beta (80)

Hi

Im getting an error while comparing with a branch (using -b option) or running in CI mode (using -m option). Backtrace attached below.

Traceback (most recent call last):
	23: from /home/atrivedi/.rbenv/versions/2.5.5/bin/rubycritic:23:in `<main>'
	22: from /home/atrivedi/.rbe

currently, we have a version lock on vee-validate.

We have to find a solution to upgrade to the latest version or switching out the validation logic.

As mentioned by @tamer-mohamed we should use the default error messages provided by the validation library, but we have to make sure to lazy-load the locales to keep the bundle size small.