I saw there's a nice way of defining flow parameters using a Pydantic basemodel. But does anyone know a setting or similar that might exist to order the attributes the same way? We've had a few people trip up because the model is defined with start and then end time, but prefect shows end and then start time

Hi Samuel! I found this issue in GitHub where Nate proposed a way to enforce ordering the attributes. Maybe this will help? From what I gather, the reason it goes out of order is that the UI doesn't have any info about ordering in the OpenAPI schema.

Ah amazing, thank you. I'll add that position extra arguments. This might be a useful something to go into the docs as an aside in the Basemodel explanation of the flow parameter section 🙂