Docu: Adding the org.eclipse.ui.selection to core expression document #3001
Conversation
| @@ -38,6 +38,7 @@ Some of the variables may not be set, depending on the current application conte | |||
| | activePart | `org.eclipse.ui.IWorkbenchPart` | The active part, which can be the same as the active editor. | 3.2 | | |||
| | activePartId | `java.lang.String` | The ID of the currently active part. | 3.2 | | |||
| | activeSite | `org.eclipse.ui.IWorkbenchPartSite` | The site of the currently active part. | 3.2 | | |||
| | org.eclipse.ui.selection | Object | The current global selection if the `ESelectionService` is used. It is often used with <test/> elements with `org.eclipse.core.expressions.PropertyTester`, in programmatic core expressions, potentially with <iterate/> and <count/> elements. | 4.0 | | |||
There was a problem hiding this comment.
I wonder if you've previewed this? I ask because one has to be careful with markdown that looks like XML,
i.e., <test/> versus ><.
There was a problem hiding this comment.
The description was copied from one line below https://github.com/eclipse-platform/eclipse.platform.ui/pull/3001/files#diff-579451fec93073440823c9b658e9877518efbd6a40ae1ce5cfebea9a4aca105dR42
There was a problem hiding this comment.
But true, the original line also does not render well: https://github.com/eclipse-platform/eclipse.platform.ui/blob/master/docs/Command_Core_Expressions.md
There was a problem hiding this comment.
I'm not really sure what you are trying to tell me. It doesn't really matter where it came from if it was already wrong where it come from, but probably I miss the point about. I really am not sure what is at the targets of the two link that should draw my attention.
Maybe it's more clear if I make a picture of the following two lines:
See this line is blank: " "
This line is not: "<test/> <iterate/> <count/>"
Here is what I wrote:
Here is how it renders/previews:
I'm just trying to tell you that you need to use back quotes on markup that looks like XML element tag otherwise it will disappear and we don't want that.
There was a problem hiding this comment.
@merks your feedback was clear, is valuable and will be acted upon. (as soon as I find the time). I just tried to explain how this happened; I copied an existing line (which also has the described issue).
There was a problem hiding this comment.
| | org.eclipse.ui.selection | Object | The current global selection if the `ESelectionService` is used. It is often used with <test/> elements with `org.eclipse.core.expressions.PropertyTester`, in programmatic core expressions, potentially with <iterate/> and <count/> elements. | 4.0 | | |
| | org.eclipse.ui.selection | Object | The current global selection if the `ESelectionService` is used. It is often used with `<test/>` elements with `org.eclipse.core.expressions.PropertyTester`, in programmatic core expressions, potentially with `<iterate/>` and `<count/>` elements. | 4.0 | |
There was a problem hiding this comment.
I see. 😁
I just proposed the change without having see your comment first. It's all fine other than this detail.
Also, as a general suggestion, when changing markdown, there is really no need to wait for a build. I never do. And anything that might need to be fixed can always be fixed after the fact...
No description provided.