Bugfix: Undefined properties accessed when using the extension in APEX 22.2 #27
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
HeLau1337
changed the title
|
Hey @bjshumway, could you review this, please? |
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.
I fixed a bug where the APEX Pro extension tried to access undefined properties of the Page Designer in APEX 22.2.
In APEX 22.2 the properties
pe.PROP.USER_INTERFACEandpe.getAll().sharedComponents.userInterfacesdon't seem to exist anymore. I figured out thatpe.getAll().sharedComponents.userInterfacenow provides the necessary information instead.Resolves #24, resolves #25.
I'm sorry about the whitespace changes in the diff view btw. My IDE removed the "dead" whitespace automatically on save. Let me know if it bothers you too much.