Skip to content

Omitting Min, Max to sequence implies no check on items #157

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

Closed
gsscoder opened this issue Jun 12, 2015 · 3 comments
Closed

Omitting Min, Max to sequence implies no check on items #157

gsscoder opened this issue Jun 12, 2015 · 3 comments
Assignees
Labels
Milestone

Comments

@gsscoder
Copy link
Owner

Sorry I haven't checked if this is already filed. if yes please ping me.

I'm going to record this because working on Issue #68 on its separate development branch issue68 the problem raised.

I'm not going to fix it or writing anything (unit tests or library code) in the dedicated branch. I'll merge when ready than re-branch to solve this issue...

@gsscoder gsscoder added the bug label Jun 12, 2015
@gsscoder gsscoder self-assigned this Jun 12, 2015
@gsscoder gsscoder added this to the 2.0.0-beta milestone Jun 12, 2015
gsscoder added a commit that referenced this issue Jun 13, 2015
@gsscoder
Copy link
Owner Author

The problem was general... I'm fixing it.

gsscoder added a commit that referenced this issue Jun 13, 2015
@gsscoder
Copy link
Owner Author

I know that all 2.0 pre-rel needs more test coverage... But for now this issue maybe considered as fixed.

@gsscoder
Copy link
Owner Author

P.S. -> Correct issue name should have been: "Omitting Mix and Max causes a named option that targets a sequence to lost its values".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant