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
Array Validators & Transforms #29
Conversation
77bcffd
to
f2d7ef2
Compare
The Array Validators now work, but is a bit hacky & not future proof, and might be even wrong thats why i wait for Automattic/mongoose#8012 (comment) to get a response |
@fabioformosa & @B-Stefan if you both would have the time, could you two test it if it breaks something? |
I will move this PR / feature / parity to an 6.x (unkown yet), because of the hackyness |
It seems that this could be a better way to support this feature #25 |
your approach #29! :) |
Update from mongoose issue: as by his comment, it seems like this approach i currently use is the only option, i still feel like this is hacky, but i think its not gonna change, so i will merge it For anyone who find missing / wrong associated options, please report via a new issue, thanks |
- logger cleanup - add semver as package to check mongoose version
a0bb4c5
to
8f47131
Compare
Current State: BUT 2 tests still fail, because 2 options are missing in mongoose, otherwise, cleanup would be needed |
- upgrade mongoose to 5.7.6
The last remaining issue in mongoose got solved, so now every test is green |
- arrayProp(gh-page): add "innerOptions" & "outerOptions" - changelog(gh-page): add note that "Array Validators" are now integrated - utils(src): actually allow the use of "innerOptions" & "outerOptions"
As a note: the semver check for mongoose "5.7.6" is made, because array validators only work on 5.7.5, and in version 5.7.6 the missing options were added |
(move from original repo to this fork)
Events happened since the original PR:
r6/master
Update 1: - fixed it now? but it is really hacky and not future proof...
so more or less all tests except 2 pass:
This PR might be a "breaking" change