Luke Ridge

Given what it was, massive improvement On Tue, Feb 12, 2019, 10:06 PM OmegaHaxors I hope you've liked the changes I did to the wire registry, I worked > really...

I was doing some quick digging into the JSON formatter because SOMEHOW it still gets the feature name, seems like the expected way to handle it now is to use...

I suppose that explains why the ast from the ast lookup consists of protofbufs, do you happen to know retrieving those is also slated to be removed?

Another use case is having a custom formatter that logs metadata such as relative feature location, id, name and scenario gherkin plus the pass and fail state to with error...

Yes those is what I ultimately ended up using. A lack of a direct link from a test case to it's ast source was a little awkward at first though...

if you have any issues with my unit tests, let me know and i can expand them/rewrite them in a style consistent with what you want.

I don't think this is necessarily an issue with the alchemical boiler, but more with the way that they and the alchemical furnace interface with alembics. From what i've caught...

Other solutions might include something akin to multireddits or even a concept like meta communities that aggregate a list of communities. Could even allow communities to subscribe to other communities.

Probably make that a separate issue since the implementation of that would be entirely internal to spectrum

May as well just use rubycritic - [ ] create rubocop config that is sane - [ ] add rubycritic directive to travis and save the results somewhere