Skip to content

Conversation

@andren
Copy link
Contributor

@andren andren commented Aug 22, 2025

Addresses #53

Before

See issue above
image

After

image

Made it case-insensitive and used regex to account for drive letters other than C.

@andren
Copy link
Contributor Author

andren commented Aug 22, 2025

I only noticed now, latest commit addresses the wrong text output.

before
Export spaces C:\Users\347_____________________________ at ____-__-__ __:__:__

after
Export spaces ~347_____________________________ at ____-__-__ __:__:__

It still worked, but it was misleading text.

@Spenhouet
Copy link
Owner

@andren Is this PR ready from your side?

@andren
Copy link
Contributor Author

andren commented Aug 22, 2025

@Spenhouet yes, I tested right before my last comment. I didn't notice any additional flaws in the meantime.

The only breaking scenario I can imagine, is if someone has a Confluence space whose name starts with C:\Users\, z:\users\ or any other drive letter, case-insensitive. In this case, cf-exporter might wrongly replace that with a tilde, but I haven't tested this yet.

@andren andren force-pushed the dev/andren/powershell-tilde-expansion branch from 7c97888 to d53ff69 Compare September 4, 2025 09:34
@andren andren force-pushed the dev/andren/powershell-tilde-expansion branch from d53ff69 to 95167ae Compare September 8, 2025 13:03
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