Jason Frey
Jason Frey
@kbrock Can you take a look at this one?
@kbrock I think this is still an issue - since you're currently in MiqExpression code, can you take a look at this one?
So, as discussed, we should drop the Timelines tab from the server diagnostics as those are redundant with just navigating to the server's VM and looking at the timelines there....
Discussed a bit with @jrafanie... --- For the dropdowns, something like this would be expected **OPTIONS /api/event_streams** ```js { "EmsEvent": { "description": "Management Events", "group_names": { vm_operation: "Vm Operations", ......
cc @NickLaMuro ... I think you had started looking at this one. cc @h-kataria ... With this we also might be able to convert the various topology pages from angular...
Moving forward, I wonder if we should change our settings.yml to settings.json... This way we _can't_ introduce non-JSON stuff.
That's a weird requirement - @kbrock Do you recall why this is needed? I would think "false" should be the default if one does not pass the parameter.
Can you link to specific code...I agree it should move to the model, actually, but it depends on the specifics
I'd be ok with this in the model. I don't think it will affect specs, but if it does we could, worst case, always wrap the validation in an `unless...
@skateman I agree. Generally, constraints that apply to all users should be in the model (or even the database)...things like specific value ranges, enums, certain validations. _Some_ things we can't...