Skip to content

Conversation

@AndrzejProchyra
Copy link
Collaborator

When telling its CSS file to copy itself to a destination directory, MicCSSEntity was giving its MicCSSFile the full path, including the file basename. If the file alredy existed at that path, the MicCSSFile was attempting to delete the full path and appending the basename again, leading to an infinite loop.

This completely moves the responsibility for knowing the basename to MicCSSFile.

A proposal to fix #982 and #618

When telling its CSS file to copy itself to a destination directory, MicCSSEntity was giving its MicCSSFile the full path, including the file basename. If the file alredy existed at that path, the MicCSSFile was attempting to delete the full path and appending the basename again, leading to an infinite loop.

This completely moves the responsibility for knowing the basename to MicCSSFile.
@Ducasse
Copy link
Contributor

Ducasse commented Dec 18, 2025

Thanks a lot andrzej!

@Ducasse Ducasse merged commit e847558 into pillar-markup:dev Dec 18, 2025
0 of 2 checks passed
@AndrzejProchyra AndrzejProchyra deleted the fix-css-entity-file-overwrite branch December 19, 2025 01:58
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.

MicHTMLVisitor examples cause an infinite loop

2 participants