-
Notifications
You must be signed in to change notification settings - Fork 7
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
Markers: support optimized option #81
Comments
Even when this method does nothing, it's part of the public API. It should be deprecated with a comment mentioning that the method serves no purpose. |
Maybe we need to re-think this. The idea of removing (now deprecating) the optimized option was because the web component side doesn't have that property, there for, does nothing if the property is set on the server side addon; but it could be added to the web component, as explained here. Would that be a better approach? |
As discussed in 2023-01-16 daily, the optimized property should be added to the web-component part. Then server side addon should be updated to use that new property. |
Back to To Do as no update was done yet on related web-component ticket. |
It was decided on #43 (comment) to remove the option as it doesn't exists in the web component part and it does nothing when enabled.
The text was updated successfully, but these errors were encountered: