Petar Cvitanović
Petar Cvitanović
@cwrau I looked into your chart, and the error you are getting is because the [type](https://github.com/teutonet/teutonet-helm-charts/blob/09041d8e2dfb464c6fdceb297ad80acdb9347ef0/charts/t8s-cluster/values.schema.json#L199) of a property is defined as an array, and currently Cyclops supports only a...
> Oh, ok, how do you handle types that could be multiple? Like int / string for resources for example. Unfortunately, we currently don't. If you put `["string", "object"]`, which...
> Maybe a kind of select? So the user can choose between the types? How did you implement oneOf and such? Kinda the same way We could add a UI...
Hey @cwrau, found the issue for the common chart I mentioned. It was on our end and how we authenticate fetch OCI charts. When requesting a token from dockerhub, we...
[Arrays currently support objects and strings](https://github.com/cyclops-ui/cyclops/blob/main/cyclops-ui/src/components/form/fields/array/ArrayField.tsx). You should expand ArrayField component to support arrays of numbers and booleans as well. Let me know if you need help with the issue.
We could use https://reactflow.dev/
Sure @knav33n!
Hey @s-vamshi, looks good from the functionality standpoint, but [this field uses `enum` to define possible options](https://github.com/cyclops-ui/templates/blob/e6d32bf4ada218c744ea19558d8e273d9bfe5bdd/app-template/values.schema.json#L84). `enum` is also used by Helm and if some other value is provided...
@s-vamshi, yup, sounds good
Hey @siddhantprateek! Thanks, this will be super helpful. Write up anything you find so we can discuss it