Bilge

Results 126 comments of Bilge

Correct. I expected this message to go away when own OAuth credentials have been supplied, but it doesn't; it is always displayed.

Possible use case: some elements use one key, others use another. I think the point here is that, from a purely engineering perspective, a static option is incorrect. We know...

Seems the issue with DeepCopy has been resolved so this is no longer on hold.

There are a couple of problems with removing `CachingConnector` in lieu of storing the cache within Porter herself: 1. The same cache would be used for all Porter providers, whereas...

A better idea might be *production mode* that removes some unnecessary checks, such as type or method checking, assuming the same code has already been tested prior to production release...

@a-barzanti You appear to be talking about the `ProviderResource` interface but the `Formatter` interface would not share any similarity. I imagine formatters would look something like the following. ``` php...

> If you have a formatter the ProviderResource will always be the same This is incorrect. A formatter and a resource have different responsibilities. A formatter takes raw data and...

If I may share my thoughts... this comes down to one of two things: either COMB is part of this library now and for the future or it is not...