Skip to content

Docu: Adding the org.eclipse.ui.selection to core expression document#3001

Open
vogella wants to merge 1 commit intoeclipse-platform:masterfrom
vogella:core-expression-docu-update
Open

Docu: Adding the org.eclipse.ui.selection to core expression document#3001
vogella wants to merge 1 commit intoeclipse-platform:masterfrom
vogella:core-expression-docu-update

Conversation

@vogella
Copy link
Contributor

@vogella vogella commented May 22, 2025

No description provided.

| 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 |
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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 ><.

image

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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:

image

Here is how it renders/previews:

image

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.

Copy link
Contributor Author

@vogella vogella May 23, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@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).

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
| 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 |

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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...

@github-actions
Copy link
Contributor

Test Results

 1 824 files  ±0   1 824 suites  ±0   1h 47m 26s ⏱️ + 14m 55s
 7 925 tests ±0   7 697 ✅ ±0  228 💤 ±0  0 ❌ ±0 
23 862 runs  ±0  23 114 ✅ ±0  748 💤 ±0  0 ❌ ±0 

Results for commit 4953b49. ± Comparison against base commit a9ec6c9.

@vogella vogella force-pushed the core-expression-docu-update branch from 4fc82a8 to 84eb663 Compare March 15, 2026 12:31
@vogella vogella requested a review from merks March 15, 2026 12:35
@vogella vogella force-pushed the core-expression-docu-update branch from 84eb663 to 5b4a020 Compare March 15, 2026 12:36
@merks
Copy link
Contributor

merks commented Mar 15, 2026

This looks inconsistent with respect to the other table entries:

image

I guess it was never really previewed in the past:

image

It would be nicer if section titles were title case:

image

Do the changes need to be multiple commits or could we do them with a single commit?

@vogella
Copy link
Contributor Author

vogella commented Mar 16, 2026

I will push an update of the PR for the errors I find.

… markdown

Add org.eclipse.ui.selection variable to the variables table and fix
markdown rendering throughout the document by wrapping XML elements
in backticks so they display correctly. Also update section titles
to use title case for consistency.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@vogella vogella force-pushed the core-expression-docu-update branch from 5b4a020 to f185abc Compare March 16, 2026 07:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants