Hey. Just a question. Can we add possibility to extend from single string not just from array? So it will work like other linting libraries (eslint, stylelint, etc.).

package.json

"babel":  {
  "extends": "shared-tools"
},
"commitlint": {
  "extends": [
    "shared-tools"
  ]
},
"eslintConfig": {
  "extends": "shared-tools"
}

today on my RSS Feed I found this great article do you think is a good idea to add it on the best practice?

I am a fairly inexperienced developer who might benefit from a wiki page explaining when you'd use this library and what it solves that the base .net framework does not.

I was under the impression that .Net core had assembly scanning already. Does this just make it more user-friendly or is it something else?

Some data sources already support DSNs but this feature is not but should be documented. The MongoDB adapter's docblock has an example on where to do this.

Data sources not or only half way supporting DSN should be changed to do so.

	// Output:
	// x = 1

This style of comments is used in example tests.

how to:

• How to configure for standalone apps
  • Single connection
  • Multiple connections
• How to configure using a properties file
• Override form system environment vars
• Override from system properties
• Configure and override in code.
• Configure and override in ActiveWeb apps
  • Configure DB-Migrator
  • Configure connection pools

Sometimes virtual functions are costly, sometimes not. Show both examples in this repo.

As suggested in #23 by @peci1:

Virtual functions might be costly if the function is called often. Maybe the code could have a non-virtual function OftenCalledFunction and a virtual NotSoOftenCalledFunction. But that decision is on you.

what

• Document usage of stage parameter
• Explain why the term stage is used rather than environment

why

• Users may not be accustomed to the nomenclature due to commonly misused usage of the term stage

references

can you give me some idea why the term 'stage' was chosen over 'environment'? In the label module?

A "stage" is where software performs (e.g. runs)

The link to the chat has an issue. Not sure how to fix it.

@EvgeniiR @peter-gribanov @alexgivi @fox-hellraiser @WoZ @gotterdemarung
Господа, прошу вас о конструктивной критике и доводам по следующим статическим анализаторм psalm vs phpstan vs phan vs (ваш вариант). Хочу помимо idea инспекций / кодстайла добавить более нейтивные валидаторы кода, для запуска например через CI.
Для проверки стиля я предполагаю использовать PHP_CodeSniffer, но для остальног

I'm wondering, does it really make sense to add documentation to our functions, if they're barely a wrapper to the original ones?

Unless there are gotchas, I would just leave:

/**
 * @link http://php.net/manual/en/function.xxx.php
 */

If we change something apart from the name of the function itself, we could just add a note:

/**
 * @link http://php.net/manual/en/

Eg. the convention

TheAssembly.WithNameMatching("MyApp.DbUp")
  .MustConformTo(Convention.MustHaveFilesBeEmbeddedResources(".sql"))
  .WithFailureAssertion(Assert.Fail);

Does not detect files that have been imported like

<ItemGroup>
  <EmbeddedResource Include="Scripts\*.sql" />
</ItemGroup>

Time of year to review this, and I'm spotting typos I somehow missed before.
Opening an issue as a reminder that I need to fix them, or let someone contribute. I'm away from my dev machine currently on travel so opening an issue to prevent losing track