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.

Sign up for GitHub

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

Jump to bottom

Improve key parsing logic #42

Closed
karataliu opened this issue Feb 28, 2015 · 3 comments
Closed

Improve key parsing logic #42

karataliu opened this issue Feb 28, 2015 · 3 comments
Labels
legacy Feature planning from previous teams P4
Milestone
1.0

Comments

@karataliu
Copy link
Contributor

karataliu commented Feb 28, 2015 •
edited by chinadragon0515
Loading

RestierQueryBuilder::GetPathKeyValues

Current parsing implementation does not allow key values to contain commas or equal.
@karataliu karataliu added the todo label Feb 28, 2015
@lewischeng-ms lewischeng-ms added this to the v0.4 or later milestone Aug 4, 2015
@lewischeng-ms lewischeng-ms modified the milestones: 0.5 or later, 0.4.0 Nov 5, 2015
@lewischeng-ms lewischeng-ms self-assigned this Nov 5, 2015
@chinadragon0515
Copy link
Contributor

Depending on the WebAPI to make KeyValuePathSegment.Values collection public (or have the parsing logic public).

@chinadragon0515 chinadragon0515 removed this from the 0.5 milestone Jul 29, 2016
@chinadragon0515 chinadragon0515 added this to the 1.0 milestone Aug 9, 2016
@biaol-odata biaol-odata added the P4 label Jun 9, 2017
@robertmclaws robertmclaws added the legacy Feature planning from previous teams label Jul 3, 2019
@robertmclaws
Copy link
Collaborator

Thanks for your input! We are resetting the project as we move to (finally!) ship 1.0. While we are closing this for now, we will re-address legacy feature requests at a later date. Please be sure to check out the latest nightly builds (and the upcoming 1.0 Beta 2 build) and let us know if you run into any issues. Thanks again!

@robertmclaws
Copy link
Collaborator

Thanks for your input! We are resetting the project as we move to (finally!) ship 1.0. While we are closing this for now, we will re-address legacy feature requests at a later date. Please be sure to check out the latest nightly builds (and the upcoming 1.0 Beta 2 build) and let us know if you run into any issues. Thanks again!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
legacy Feature planning from previous teams P4
Projects
None yet
Milestone
1.0
Development

No branches or pull requests
7 participants
@markdstafford @lewischeng-ms @robertmclaws @karataliu @chinadragon0515 @robward-ms @biaol-odata