-
Notifications
You must be signed in to change notification settings - Fork 70
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
[Feature Request] safer safenames #1921
Comments
FYI - I originally designed safenames to help with real-world data ingestion using Datapusher+ for CKAN - especially with spreadsheet header names. That's why its defaults are heavily informed by CKAN requirements. I can certainly make it "safer" using your proposal, though I have to prioritize CKAN data ingestion. Perhaps, I can just add a new command called |
hmm .. would the creation of a new subcommand with similar functionality be counter-intuitive ? |
Point taken... I'll just have to add it to |
how about |
Yes... that's the easy part... The part that I'm thinking about is how the JSON output formats will work... |
while the current safename option are many and database column-name safe, actual naming schema might not be what the user wants.
my proposal would be the (s)afe mode as defined be the following steps:
[:alnum:]
with "_"[_]+
with "_"(s)afe mode should operate in ascii-chars-only mode, (S)afe mode should work in unicode-chars mode.
The text was updated successfully, but these errors were encountered: