Parker Abercrombie
Parker Abercrombie
For Clipper, priority is parameters, then resources, then computed attributes.
Being able to upload CSV directly would be nice. Turning CSV into GraphQL greatly increases the payload size. Long term I think we will need a more robust solution than...
To re-state the problem: we would like support optional activity parameters. Clipper wrote a custom value mapper for the java.util.Optional type, but we'e run into a number of problems trying...
Agree that all of this would be really useful in the UI.
Related request #459
Probably "0d 2h 3m 25s 770ms 0us" is preferred. Our plans are usually weeks to years long.
This would help Clipper close out one of our simulation requirements.
In most cases Clipper would prefer to default to least privileged role to avoid users making unintentional changes.
Closing as obsolete, we have not seen issue since it was originally reported.
Related to https://github.com/NASA-AMMOS/aerie-ui/issues/1481