[
https://issues.apache.org/jira/browse/NIFI-2900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15628629#comment-15628629
]
ASF GitHub Bot commented on NIFI-2900:
--------------------------------------
Github user simplesteph commented on the issue:
https://github.com/apache/nifi/pull/1136
hi @mcgilman , pain commit but it should be good. the resulting
`swagger.json` doesn't have any datetime, which makes the api compliant in that
regard. Not sure when 2.0 is planned, and not sure how you track todos against
it, but converting these fields back to compliant datetime is a must for the
next version of the api
> DateTime API Endpoints don't respect RFC 3339
> ---------------------------------------------
>
> Key: NIFI-2900
> URL: https://issues.apache.org/jira/browse/NIFI-2900
> Project: Apache NiFi
> Issue Type: Bug
> Components: Core Framework
> Affects Versions: 1.0.0
> Reporter: Stephane Maarek
>
> Hi,
> the endpoint /flow/process-group/id is supposed to return lastRefreshed as
> part of ProcessGroupFlowDTO as a DateTime, as indicated here:
> lastRefreshed string (date-time) optional The time the flow for
> the process group was last refreshed.
> as it currently stands, what I am getting doesn't look like a timestamp:
> "lastRefreshed":"14:02:46 AEDT"
> I'm not sure how much of the overall API is affected
> Edit:
> Actually, it seems every date a "date-time" is created we expect the format
> "HH:mm:ss z".
> As per the OpenAPI specs, if a field is annotated "date-time", it should
> respect the RFC 3339 convention
> (https://github.com/OAI/OpenAPI-Specification/blob/master/versions/2.0.md#data-types).
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
