Sebastian Good

I'm just going to add a couple more suggestions here: ``` next quarter next {month} e.g. 'next December' or 'next Jan' ``` Here are some more 'abstract' ones: ``` next...

This reminds me of the way we (in the UK) say phone numbers. Lets, say you have the following UK phone number; 07770 11 22 33. There are two different...

This is a nice idea, how do you think we could differentiate your three categories in text? I would assume there would have to have a system in place to...

The other thing that may be worth noting is that the processing of `numbers` like this would take longer, as the `#Value` would most likely have to split into ngrams...

Here are some possible thoughts. Example table with decimals/separators. ``` The simple ones: 100,000,231.237 -> Separator: ',', Decimal: '.' 1,373.432 -> Separator: ',', Decimal: '.' 100.000.231,237 -> Separator: '.', Decimal:...

#361 Might fix this :eyes: If the issue that you're facing is when the language scope name changes

For reference this is an example of what I think is incorrect: First request a token: ``` [~/github/saml-oauth2 (master)] $ curl -v 'http://localhost:8080/oauth/authorize?client_id=123&response_type=code&scope=read&state=31232' > GET /oauth/authorize?client_id=123&response_type=code&scope=read&state=31232 HTTP/1.1 > Host: localhost:8080...

@whatwewant I referenced the relevent comment to the relevent part of the spec in my description. To quote: [redirect_uri] REQUIRED, if the "redirect_uri" parameter was included in the authorization request...

If you're using yaml you can just use multiline strings, eg: ```yaml with: changelog-types: |- [ { "type": "feat", "section": "Features", "hidden": false }, { "type": "fix", "section": "Bug Fixes",...

There is a partial bug here, the oil geyser (on the right) is as it's meant to be. On the left there is a bug where oil appears on top...