Deprecated and replace the miss-spelled MODEL_ELEMEMT internal property #179
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
MODEL_ELEMENT property.
NiklasRentzCAU
force-pushed
the
nre/deprecate-modelElememt
branch
from
b8a076a to
01a3020
Compare
|
Nice, I never saw that 🤪 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This typo was bugging me for quite some time, now it is no longer. To not break the API of any dependent projects, the old property is still kept as a deprecated property, pointing to the same object as the new one. This leaves us the option to replace the property entirely in some future release.