-
Notifications
You must be signed in to change notification settings - Fork 78
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
Implemented optional data validation #118
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This needs a unit test as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Sorry for giving you a lot of work, just want to make sure that the DataStore2 codebase is as solid as can be.
Co-authored-by: boyned//Kampfkarren <[email protected]>
Co-authored-by: boyned//Kampfkarren <[email protected]>
Co-authored-by: boyned//Kampfkarren <[email protected]>
Co-authored-by: boyned//Kampfkarren <[email protected]>
Co-authored-by: boyned//Kampfkarren <[email protected]>
Co-authored-by: boyned//Kampfkarren <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You can click "Add suggestion to batch" to combine them all into one commit, by the way.
Co-authored-by: boyned//Kampfkarren <[email protected]>
Can you please provide proof that you ran the tests and they pass? I'm trying to get them running on CI. |
Tests run on CI now, merge from latest master. |
Ugh, that specific error is not your fault. I'll look into it. |
I think I don't have the ability to run tests on PRs since you don't have the authentication token, I'm going to clone your branch and test it on there. |
Your tests failed--#121 Please make a good attempt to run the tests locally. All it should take is:
|
I'm getting |
I'd recommend doing a bisect, removing paths from the project.json until it works, so you know which path in specific is causing the issues. Make sure your Rojo is up to date as well. I know what is causing the test failures, but I want to make sure you know how to run the tests yourself! |
How, I cannot for the life of me figure this out. Edit: Might have figured it out |
Request review from me when you have something that works so I can run it on the CI runner. |
I have been trying to figure this out for a week now and I'm still none the wiser. I'm still stuck with the cryptic error messages above. The same code without the unit testing works completely fine though so the errors must be caused by TestEZ somehow 🤔 |
end | ||
|
||
dataStore:SetValidator(testValidator) | ||
expect(dataStore:Set("nope")).to.throw("Attempted to set data store to an invalid value during :Set") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You need the function
there because that's what's actually pcalled. The way you have it now looks like :Set
returns a function that you're checking.
Implemented #64