Kurtis Rainbolt-Greene
Kurtis Rainbolt-Greene
So I just used this as a patch in my own project and I'm noticing that `Strict::String.enum([:a, :b, :c])['a']` raises a constraint error. First off I'm not sure why that...
Honestly just adding the grid to the output would be a huge boon, then people could do the commenting bit themselves.
I don't understand how the code I changed affects the code broken in the tests 🤔
I'm good with either option.
While jsonapi is allowed as a top level property, it is *not* allowed at the resource document level
``` json "resource": { "description": "\"Resource objects\" appear in a JSON API document to represent resources.", "type": "object", "required": [ "type", "id" ], "properties": { "type": { "type": "string" },...
Seems like a better approach would be to have includes no-op at the Policy level?
What is `commitlint` talking about here?
I'm on a Macbook, but I'm betting they're getting this error: ``` Gem::Ext::BuildError: ERROR: Failed to build gem native extension. /Users/krainboltgreene/.rvm/rubies/ruby-2.1.2/bin/ruby extconf.rb creating Makefile make "DESTDIR=" clean make "DESTDIR=" compiling...
Have you noticed any differences between testing against a free vs hobby vs standard vs professional vs performance dyno?
What's the reason for wanting to see a suspended account in your blocks/mutes? If they're suspended, do you really care to unblock/unmute?