collective / collective/stxnext.staticdeployment
use xml parsing instead of regular expressions and text replacement
Open
- Dominant language
- Python
- Stars
- 10
- Forks
- 4
- PR merge metrics
- No merged PRs in 30d
Description
This is more something that should be done long term in the product that I might contribute to doing eventually.
Right now you can run into problems where the transformation of one url can also change others that partially match that url. If we moved all transforms to use lxml instead of regular expressions, it'd fix this issue. I had to do an ugly hack for now though...
Also, we should probably use lxml instead of beautiful soup since it's pretty standard.
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.