-
Notifications
You must be signed in to change notification settings - Fork 18
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
Properties: some improvements #64
Conversation
@danyaljj : Is your last PR working really? val listIntAttributeArrayOldWay = property[Document]("listInt") {
x: Document => List(1)
}
} and then this : val x6=listIntAttributeArrayOldWay(tests.head) does not compile where val listIntAttributeArrayOldWay = intAttributesArrayOf[Document]('listInt) {
x: Document => List(1)
} |
@kordjamshidi @christos-c @sameersingh This PR is ready for review. Comments are welcome! |
Have you run an example with mixed features? |
No, any problem? |
@kordjamshidi have you noticed any issue? |
@@ -8,15 +9,31 @@ class propertyTest extends FlatSpec with Matchers { | |||
"properties" should "work!" in { | |||
import toyDataModel._ |
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.
@kordjamshidi I have this unit test in which I test all of the properties.
I think it just did not work, even in Lbjava. |
What file? Where? What is the error? |
I have not run it to see what is the error, but I guess the mixed attributes should be checked as those did not work. You can try an example in Lbjava first. I guess the code in this file: |
@danyaljj , does this version work when calling properties on instances? I need a working version, and I am going to accept this PR if this is working-- because your previous PR does not work. |
As I mentioned it removes a bug I had in the previous version. |
Sorry if I miss something here, it would be helpful if you point me to the place in your test unit that calls the property by its name and directly applies on an instance like the example I mentioned: |
I am coming to your office! |
This is ok for me to merge now. |
Properties: some improvements
Moved to a Phrased based Data model
With this PR the new definitions for properties should be fully functional. Also,
Note: I still need to remove the old property definitions and change the core and existing instances accordingly. I will do these in another PR. And fixing the naming patterns inside the properties( issue #33 ) for another PR.