-
Notifications
You must be signed in to change notification settings - Fork 149
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Dependency stringcase
seems to be unmaintained
#1655
Comments
pierrecamilleri
changed the title
Dependency
Dependency Apr 29, 2024
stringcase
seem to be unmaintainedstringcase
seems to be unmaintained
I had a look into this - given that stringcase is also MIT-licensed, and to be sure of not changing behavior in frictionless, I would suggest copying the functions we use into frictionless as-is. And then fixing any deprecations. Happy to open a PR if that sounds ok |
Sounds good to me, thanks ! |
Lincoln-GR
pushed a commit
to LincolnPuzey/frictionless-py
that referenced
this issue
Jan 16, 2025
Lincoln-GR
pushed a commit
to LincolnPuzey/frictionless-py
that referenced
this issue
Jan 16, 2025
Lincoln-GR
pushed a commit
to LincolnPuzey/frictionless-py
that referenced
this issue
Jan 16, 2025
pierrecamilleri
added a commit
that referenced
this issue
Jan 27, 2025
- fixes #1655 Commits: - Vendor `stringcase` library - Fix deprecation warning in it - Swap so it is used, remove dependency on actual library --------- Co-authored-by: Pierre Camilleri <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Context
Frictionless has
stringcase
as a dependency.From what I can see, it is used for conversion of strings to snakecase or camelcase.
Issue
The stringcase dependency seems not maintained anymore.
It triggers for instance
DepreciationWarnings
:Proposition
I would either remove the dependency and include all code to perform this in frictionless-py, or use the Casefy alternative replacement of this library.
Do you have a preferred option? I can propose a Pull Request.
The text was updated successfully, but these errors were encountered: