Jordan Pellizzari
Jordan Pellizzari
I think this is a webpack or babel problem
This was something I considered when building the docs portion of this project. I was worried that the example code had more complexity than was necessary to use the component....
There may be a hidden "cool product feature" here. We had originally built the debugging UI for internal use only, but it is very possible that users can't get a...
Notes from triage: * Because we are using TS, we don't need the `react/prop-types` * We don't really care about the `displayName`, we can disable `react/display-name` * Let's enforce `exhaustive-deps`...
Let's treat this like a Spike and research whether or not each of these are useful.
We don't feel strongly about the `myVar[0]!`, since it helps us deal with `gRPC` rough edges. This is just a chore to keep everything consistent in both EE and OSS.
@LappleApple I saw a design that resembled it a while back. The Argo view shows `Pod` status by `Node`, which is fairly trivial in a single cluster context. The WeGO...
> would be displayed under their parent objects to show the view like flux tree view. > > > For example something like this: > > Kustomization/flux-system/flux-system > > ├──...
> It would not be for multi-cluster. Only for each cluster and be a replication of the flux tree view. I would be very surprised if this is possible in...
> cc @jpellizzari you touched the bitbucket auth stuff recently, would it be tricky to add github-app / (clientid/clientsecret) support? I guess falling back to the device-auth that we currently...