Skip to content

Conversation

@Dani-Hub
Copy link
Contributor

Add "svg" to list of supported file extensions for images

…itor

Add "svg" to list of supported file extensions for images

Signed-off-by: Daniel Krügler <[email protected]>
@Dani-Hub Dani-Hub force-pushed the #2025-SVG-icons-not-supported-by-extension-point-editor branch from b6509bd to a664af1 Compare October 17, 2025 17:30
@Dani-Hub
Copy link
Contributor Author

Can someone please help me with the ECA problem? I logged in again and revalidated my ECA but it still does not validate here. Have recently the commit rules changed? Is my commit text incomplete?

…itor

Add "svg" to list of supported file extensions for images

Signed-off-by: Daniel Krügler <[email protected]>
…oint-editor'

of github.com:Dani-Hub/eclipse.pde
into eclipse-pde#2025-SVG-icons-not-supported-by-extension-point-editor

Signed-off-by: Daniel Krügler <[email protected]>
@Dani-Hub Dani-Hub force-pushed the #2025-SVG-icons-not-supported-by-extension-point-editor branch from 642ce73 to 993bf24 Compare October 18, 2025 05:47
@HannesWell HannesWell changed the title * Issue #2025: SVG icons not supported by extension point editor Support SVG icons in extension point editor Oct 18, 2025
Copy link
Member

@HannesWell HannesWell left a comment

Choose a reason for hiding this comment

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

Thank you for your contribution.

Can someone please help me with the ECA problem? I logged in again and revalidated my ECA but it still does not validate here.

This is indeed a bit strange as the ECA overview page also shows your mail validated once but four times as not validated and it looks like the same mail:
https://api.eclipse.org/git/eca/status/gh/eclipse-pde/eclipse.pde/2026

Have recently the commit rules changed? Is my commit text incomplete?

Actually not. But your three commits, including a merge commit seem to be a bit strange and maybe this confuses the tool.
Please squash your change in one commit, with a meaningful message. Ideally the message references the issue by its full URL. E.g. at the end using:

Fixes https://github.com/eclipse-pde/eclipse.pde/issues/2025

Then rebase that commit on top of the current master and force push it to the branch of this PR to update it.

Thanks in advance.

"attribute", "value"}; //$NON-NLS-1$ //$NON-NLS-2$

private static final String[] VALID_IMAGE_TYPES = {"png", "bmp", "ico", "gif", "jpg", "tiff"}; //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ //$NON-NLS-4$ //$NON-NLS-5$ //$NON-NLS-6$
private static final String[] VALID_IMAGE_TYPES = {"png", "bmp", "ico", "gif", "jpg", "tiff", "svg"}; //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ //$NON-NLS-4$ //$NON-NLS-5$ //$NON-NLS-6$ //$NON-NLS-7$
Copy link
Member

Choose a reason for hiding this comment

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

Since you are touching that line anyways, could you also modernize it by using a List?

Suggested change
private static final String[] VALID_IMAGE_TYPES = {"png", "bmp", "ico", "gif", "jpg", "tiff", "svg"}; //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ //$NON-NLS-4$ //$NON-NLS-5$ //$NON-NLS-6$ //$NON-NLS-7$
private static final List<String> VALID_IMAGE_TYPES = List.of("png", "bmp", "ico", "gif", "jpg", "tiff", "svg"); //$NON-NLS-1$ //$NON-NLS-2$ //$NON-NLS-3$ //$NON-NLS-4$ //$NON-NLS-5$ //$NON-NLS-6$ //$NON-NLS-7$

@Dani-Hub
Copy link
Contributor Author

I'm not so familar with squashing, therefore I decided to close this puull request in favour for a new one (#2030)

@Dani-Hub Dani-Hub closed this Oct 18, 2025
@HannesWell
Copy link
Member

I'm not so familiar with squashing, therefore I decided to close this pull request in favour for a new one (#2030)

Please try to avoid it for future contributions as this causes extra noise and makes it harder to follow discussions if they are distributed over multiple PRs.

You can squash existing PRs with EGit for example in the History view of Eclipse using the context menu. Just select the consecutive commits you want to squash, right-click on them and select via Modify -> Squash:

Alternatively/additionally you can also Amend an existing commit in EGit's Git staging view:

And to force push you can for example select the corresponding check-box in the EGit push dialog (the details depend a bit on your exact workflow):

On the CLI you can of course push with --force/-f.

Don't hesitate to ask if you have more questions :)

@Dani-Hub
Copy link
Contributor Author

Thanks very much about the explanation about squashing! Btw.: I actually did amend all my original commits of my first pull request, I'm surprised that it appeared as individual commits to you. Anyway, the problem is now solved, thanks again for your support!

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