-
-
Notifications
You must be signed in to change notification settings - Fork 2.9k
Sync Javascript Binding - Add support for property interception #3935
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
Conversation
❌ Build CefSharp 97.0.80-CI4345 failed (commit 2d6bd9d484 by @) |
@amaitland Kindly let me know if I am missing anything for the failing test case. |
The failing test is #3867 Property interception is not available in .Net Core and will need to be excluded with an if def see https://github.com/cefsharp/CefSharp/blob/master/CefSharp/Internals/JavascriptObjectRepository.cs#L197 for example. |
✅ Build CefSharp 97.0.80-CI4346 completed (commit 3869b1e24d by @santoshmgh) |
✅ Build CefSharp 97.0.80-CI4348 completed (commit 444a31e58a by @santoshmgh) |
@amaitland Are we good to merge these changes? |
This will need to be addressed before this PR can be considered for merge. A unit test should also be added. Testing the JavaScript object repository functionality directly should be sufficient. Add test to https://github.com/cefsharp/CefSharp/blob/master/CefSharp.Test/JavascriptBinding/JavaScriptObjectRepositoryFacts.cs |
@amaitland
Additional Query |
To simplify things the whole TryGetProperty method can be excluded from the netcore implementation.
Yes. You will need to compile the netcore solution and resolve all the errors. |
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.
Comments inline
@santoshmgh Please confirm if you are planning on implementing the required changes or if the |
@amaitland I will be incorporating the above comments.. |
@amaitland Kindly let me know if I need to incorporate any other comments. |
❌ Build CefSharp 97.1.10-CI4377 failed (commit 25be78c73a by @santoshmgh) |
❌ Build CefSharp 97.1.10-CI4383 failed (commit ace575dbc4 by @santoshmgh) |
@amaitland Kindly let me know how can I run the test case from CefSharp.Test.dll locally. So that I can fix the failing test case. |
I don't see a qunit test. Can you re-add it please.
Tests can be run from within Visual Studio, nothing special required. |
❌ Build CefSharp 97.1.10-CI4384 failed (commit 29c1760294 by @santoshmgh) |
@amaitland Added the unit test cases to CefSharp.Test.JavascriptBinding.JavaScriptObjectRepositoryFacts |
❌ Build CefSharp 97.1.10-CI4385 failed (commit 46e6880dde by @santoshmgh) |
Please add a separate test case rather than modifying the existing one. |
✅ Build CefSharp 97.1.10-CI4392 completed (commit 7a34d91588 by @santoshmgh) |
@amaitland I have added a separate test case for property Interceptor. Please let me know if you want to update the test name to something else. |
Thanks. I'm not too worried about test naming, they can always be improved later without impacting anyone. |
✅ Build CefSharp 98.1.120-CI4395 completed (commit 1b5ff45b0e by @santoshmgh) |
@amaitland Please confirm if changes for property interceptor will be available as part of cefsharp 98 release. |
@santoshmgh If you look at the |
* Core - added support for property interceptor * Incorporated the review comments * Incorporated the review comments 2 * Review comments exclude trygetproperty and trysetproperty for .netcore app * Added the unit test cases for trygetproperty and trysetproperty * Fixed .net core app build failure * Added the separate test case for property interceptor Co-authored-by: sghanti <[email protected]>
Summary:
Changes:
How Has This Been Tested?
Types of changes
Checklist: