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

Allow passing new RealtimeField as string #47

Open
assylias opened this issue Nov 15, 2018 · 1 comment
Open

Allow passing new RealtimeField as string #47

assylias opened this issue Nov 15, 2018 · 1 comment

Comments

@assylias
Copy link
Owner

If a new realtime field is exposed by the Bloomberg API, it can't be access until the RealtimeField enum is updated.

Allow to pass a realtime field as a string to the SubscriptionBuilder.

@Kurry
Copy link

Kurry commented Dec 8, 2018

Yes! Both a Collection<String> fields and String field, the number of real time fields are in the hundreds if not thousands, and so I think this makes the most sense. I have to do this in my own fork. Also, adding the ability to add subscription options would be helpful. I like this change because really, you could just get rid of the SubscriptionHolder class. Not only should you allow people to pass new RealtimeField, you also should allow them to pass strings for subscription options.

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