Phillip Kessels

Here's how I solved it using dry-monads (someone else mentioned it on another issue [already](https://github.com/varvet/pundit/pull/655#issuecomment-812509205)): ```ruby class ThingPolicy < ApplicationPolicy include Dry::Monads[:result] def user_completed_thing? user.completed_things.include?(record.thing) end def user_bought_thing? user.orders.find_by(orderable: record).present?...

Not sure if there are any tests to be added here or documentation updated

Fix here: https://github.com/honeybadger-io/honeybadger-js/pull/1415

I actually noticed another error: Honeybadger (the react package specifically) imports `Component` from react. I receive an error now during build stating that `react` doesn't export `Component`. When I run...

Sorry for taking a while to come back to you, @subzero10 . After finally deploying the update today I can confirm it working. I have just received my first frontend...

With the help from some comments on this and other issues I came up with this solution: https://www.npmjs.com/package/relay-transform-scalar I couldn't yet figure out how to make the compiler insert the...

I adjusted the script to work like this: ```bash set -ex # Builds a NanoVNASaver.app on MacOS # ensure you have pyqt >=6.4 installed (brew install pyqt) # export VENV_DIR=macbuildenv...

It looks like you are starting one of the scripts. What happens if you just double click the app in the dist folder? I did get that error in earlier...

Was there anything in the output of the build script above that seemed suspicious? I did specify `set -ex` so it aborts upon failure, but there might be a warning...

So I tried to build again just to compare the warnings and I get the same ones. The ones about some SDK version I mean. So it seems that is...