Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1136
Thanks @simplesteph! This has been merged to master (without the changes to
the TimeAdapter). I've created a JIRA [1] to revisit the entirety of the Rest
Api with regards to the OpenApi spec when
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
Github user simplesteph commented on the issue:
https://github.com/apache/nifi/pull/1136
Sorry I haven't had the time to work on it just yet... Agree with all the
above
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If
Github user mike42 commented on the issue:
https://github.com/apache/nifi/pull/1136
@mcgilman- I would also like to see the REST API change in the next major
release. Date localisation should be moved to the front-end, as only the
browser knows the user's locale and timezone.
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1136
Hey sorry, I was traveling yesterday. I don't see your most recent changes.
Can you double check that you've pushed them?
---
If your project is set up for it, you can reply to this email and have
Github user simplesteph commented on the issue:
https://github.com/apache/nifi/pull/1136
I think then we need to add `dataType = "string"` in the annotation to
every field `DateTime` that uses any `TimeAdapter` or `DateTimeAdapter`.
Hopefully this way the format won't be shown as
Github user mcgilman commented on the issue:
https://github.com/apache/nifi/pull/1136
NiFi follows the semantic versioning guidelines. What your suggesting is
changing the meaning of those fields. They are strings that are meant to be
human-readable (one with the time and the other
Github user simplesteph commented on the issue:
https://github.com/apache/nifi/pull/1136
That could be a solution, but I believe it's a more complicated one than
just keeping the date-time annotation and make the API compliant with the
OpenAPI specs. If you create a "Time" class then
