Emelia Smith

> .well-known/solid requires: IANA hop; Solid server to 1) have storage at / and 2) update/control /.well-known/solid. The Solid Protocol has no requirement on Solid server or any Storage to...

> Cognito and KeyCloak are following the [OpenID spec requirement](https://openid.net/specs/openid-connect-discovery-1_0.html#ProviderConfig). There, the `.well-known` path starts not (necessarily) at the root of the server, rather it is appended to the issuer...

Some context worth considering here: - From the browser, via the `fetch()` API, there is no way to get information about redirects; you can either get the information about the...

@gibsonf1 unfortunately not, for 3xx responses, the fetch API automatically follows redirects, only allowing access to the final destination's information, and in manual mode, prohibits accessing the redirect's headers or...

> @ThisIsMissEm I see you are right on the status issue, although knowing what url you end up at is easy with response.url. So for the Solid case, maybe the...

> Emelia Smith Any news? @btd1337 usually if there's news on something, then the person would say.

@jimthedev this could be fixed with specify a `peerDependency` of `commitizen @ >= 2.8.1`, meaning that everyone will get told to update if they're not up-to-date

You can see what I mean by the separation of logic here: https://github.com/ThisIsMissEm/cz-conventional-changelog/pull/1/files#diff-168726dbe96b3ce427e7fedce31bb0bcR94

I don't think you need another configuration option here, just using `maxLineWidth` should be okay. The automatic wrapping actually happens in cz-conventional-commit: https://github.com/commitizen/cz-conventional-changelog/blob/master/engine.js#L206

@bertho-zero oh, neat, you've been working on this as well; I didn't know about `scope-enum` rule though. Here's my progress so far, it's trying to change as little code as...