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

Access array index in I/O mapping #2366

Closed
iamtakingiteasy opened this issue Apr 18, 2019 · 3 comments

Comments

2 participants
@iamtakingiteasy
Copy link
Contributor

commented Apr 18, 2019

How to access an array index with current I/O mapping?
#2172 seems to remove JSON path notion, so how arrays are supposed to be subscripted now?

@iamtakingiteasy

This comment has been minimized.

Copy link
Contributor Author

commented Apr 18, 2019

Quick glance suggests that PR has not made any adequate substitute for handling array indexing, removing also any documentation reference and tests that involved such.

@saig0

This comment has been minimized.

Copy link
Member

commented Apr 18, 2019

You are right. Currently, it is not possible to access an array by index. We removed the function because it was not really useful in this form.

What do you need exactly?
Please describe your use case in detail. This will help us to build the feature in the right way.

@iamtakingiteasy

This comment has been minimized.

Copy link
Contributor Author

commented Apr 19, 2019

Currently I had my I/O mappings fully refactored, this not an issue to me any more.

I agree that being lazy on writing actual unwrappers for cases where data comes in tuple-arrays was not a good design decision, so I had a rightful backfire. Just did not expected it to be that soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.