We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hi team, do you think it is possible to use datetime type instead of ScheduleSpec? Arm team is suggesting us to change it.
type ScheduleSpec struct { Date string json:"date" Time string json:"time" Zone string json:"zone" }
json:"date"
json:"time"
json:"zone"
type StageSpec struct { ... Schedule *ScheduleSpec json:"schedule,omitempty" }
json:"schedule,omitempty"
type StageSpec struct { ... Schedule time.Time json:"datetime" }
json:"datetime"
The text was updated successfully, but these errors were encountered:
Think of usability scenarios: Schedule a deployment at 5PM on Friday (local time).
Sorry, something went wrong.
OpenAPI spec is using ISO 8601. It will support offset date time(local time). I think we can use the same standard to parse in symphony code. https://www.iso.org/iso-8601-date-and-time-format.html
fixed by the PR: #276
FireDefend
No branches or pull requests
Hi team, do you think it is possible to use datetime type instead of ScheduleSpec? Arm team is suggesting us to change it.
type ScheduleSpec struct {
Date string
json:"date"
Time string
json:"time"
Zone string
json:"zone"
}
type StageSpec struct {
...
Schedule *ScheduleSpec
json:"schedule,omitempty"
}
type StageSpec struct {
...
Schedule time.Time
json:"datetime"
}
The text was updated successfully, but these errors were encountered: