Skip to content
New issue

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

"ISO8601" as alias for "DateTime" #2654

Closed
fgalan opened this issue Nov 10, 2016 · 5 comments
Closed

"ISO8601" as alias for "DateTime" #2654

fgalan opened this issue Nov 10, 2016 · 5 comments

Comments

@fgalan
Copy link
Member

fgalan commented Nov 10, 2016

In order to ease integration with IOTA versions using TimeInstant of type ISO8601, Orion should support this late string as an alias of DateTime.

This would be something to mention in the "NGSIv2 implementation notes" document, but it shouldn't be included as part of NGSIv2 specification (which should stick to "DateTime").

@fgalan
Copy link
Member Author

fgalan commented Dec 20, 2016

Implemented by PR #2775. @iariasleon pls have a look and close if you find it ok.

@iariasleon
Copy link
Contributor

iariasleon commented Jan 16, 2017

This issue will be passed to the QATestPending milestone.

Tested in INT but still in component.

See pepflows/024_pep2cbv2_iso8601support.feature into iotp-qa repository.

@iariasleon iariasleon modified the milestones: QATestPending, 1.7.0 Jan 16, 2017
@fgalan
Copy link
Member Author

fgalan commented Jan 16, 2017

Other times we have wait to the end of the sprint before moving QA pending issues of backlog type to QATestPending milestone. However, it you are sure at the present moment of that (because there is no time for testing it within the sprint or you plan to use the time to test other more important issues already in QATestPending) is also ok with me.

@iariasleon
Copy link
Contributor

covered in E2E in features/pepflows/024_pep2cbv2_iso8601support.feature

@fgalan
Copy link
Member Author

fgalan commented Feb 15, 2018

Issues in milestone QATestPendingE2ECovered are going to be closed (it is not realistic to think we would have people working on behave testing at the present moment). However, issue is labeled with QATestPending label in the case things change and we need to recover it.

@fgalan fgalan closed this as completed Feb 15, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants