Keith Smiley
Keith Smiley
When prompting for a user's credentials we should validate their radar auth instead of just saving bogus auth.
The radar "API" supports adding multiple attachments to a single radar. Right now the UI limits you to only one attachment. We should add UI for handling more than one.
We might want to support duping radars that don't include the `Description` section, and just use everything before the first field as the description. https://github.com/br1sk/brisk/pull/75#issuecomment-310782541
Currently if you start posting a radar with Brisk, and go to a different app, the window is closed in the background, and it's unclear whether or not the radar...
When duping radars you can end up in some weird places with lots of information in Version / Configuration. Ideally these would probably just be text views like everything else,...
As a new user signing up, if you want to post to open radar, it's not super clear how to do so. I think we should allow users to enter...
Currently you can edit text fields after you being submitting a radar. We should disable these and re-enable them when posting completes.
This API allows us to mostly remove `#if` conditionals which enables cross compilation from macOS -> Linux. It also removes the thrashing of Package.resolved if you compile in a docker...
If you have a rule that has a list attr that isn't known (or at least isn't just `deps`) like this: ```bzl some_rule( name = "foo", something = [ "foo",...
With the `par_binary` from [this repo](https://github.com/google/xctestrunner) which is defined as: ```python package(default_visibility = ["//visibility:public"]) load("@subpar//:subpar.bzl", "par_binary") py_library( name = 'shared', srcs = glob(['shared/*.py']), ) py_library( name = 'simulator', srcs =...