Skip to content
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

Replace usage of unicode in schemas and presets #298

Open
amercader opened this issue Sep 9, 2021 · 0 comments · May be fixed by #299
Open

Replace usage of unicode in schemas and presets #298

amercader opened this issue Sep 9, 2021 · 0 comments · May be fixed by #299

Comments

@amercader
Copy link
Member

This only affects current CKAN master (future 2.10) but flagging in advance

After ckan/ckan#6048 was merged, trying to use a schema that uses builtin functions like unicode (py2) or str fails with:

E           TypeError: str cannot be used as validator because it is not a user-defined function

The example schema that this extension ships with, and some of the presets use some of these builtin validators/converters so we should replace them with the alternatives currently used in CKAN core (ie unicode_safe).

For previous versions of CKAN I think ckanext-scheming should provide its own copies of the validators, or include them in ckantoolkit.

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 a pull request may close this issue.

1 participant