Chris Deely

also experienced this while attempting to deploy to azure using a malformed compose file. use `docker-compose -f compose-file-name.yml config` to validate and detect the errors until this is fixed

that's a great idea! Interested in working on it? On Thu, Aug 21, 2014 at 3:26 PM, caseman72 [email protected] wrote: > For > Access-Control-Allow-Origin > > It would be nice...

Easiest route is probably to look at the header value in https://github.com/chrisdeely/ForceCORS/blob/master/background.js#L47-L51 If it matches "HTTP_ORIGIN" replace with the current Host value

I have been attempting to implement this enhancement via [modifications](https://github.com/chrisdeely/jsonschema2md/commit/cd1ce34e5356cb3fe4c59a1ab544d3b7d0f9ea2f) to the `schemaProxy`, but it is clunky an error prone. I'm not familiar enough with the patterns in use, but...

I have to admit I hadn't thought about that. I haven't touched this codebase in quite a while, but I'd be open to a PR if you want to take...

@kisenka I'll happily let you take the reigns here! I obviously have not gotten back to this in a timely manner

i'm taking a look at this - the repo has moved on quite a bit since I initially made this PR, I'll see if I can adapt it to the...

I have updated my branch to re-implement this feature according to the new code style & features. the tests are all passing and the new `matchingPixelAlpha` option should allow users...