Skip to content
Snippets Groups Projects
Select Git revision
  • master default protected
  • dev protected
  • ckan-2.11.0
  • add-package-custom-fields
  • fix-adding-datasets-for-users-and-editors
  • add-auth-subroute
  • 71-migrate-custom-fields-to-ckanext-scheming
  • add-author-maintainer-information
  • fix-inline-flex-btns
  • fix-known-spatial-uri-validation
  • py3
  • 47-aktuelle-resource-einer-collection-wird-nicht-mehr-gefunden
  • 10-eingabe-der-dct-accrualperiodicity-in-weboberflache
  • v1.3
  • 2.5.3
  • 2.5.2
  • 2.5.1
  • 2.5.0
  • 2.4.7
  • 2.4.6
  • 2.4.5
  • 2.4.4
  • 2.4.3
  • 2.4.2
  • 2.4.1
  • 2.4.0
  • 2.3.1
  • 2.3.0
  • 2.2.0
  • 2.1.0
  • 2.0.0
  • 1.4.3
  • 1.4.2
  • 1.4.1
34 results

plugin.py

  • Thorge Petersen's avatar
    1262abf7
    Remove tag_name_validator function and its usages · 1262abf7
    Thorge Petersen authored
    The tag_name_validator function, which enforced restrictions on tag names, has been completely removed from the codebase. This change allows for unrestricted tag names, removing any validation based on the regular expression pattern. The decision to remove this function was made to align with the desired behavior of not imposing any limitations on tag names.
    
    This commit removes the tag_name_validator function and any code where it was called, ensuring that tag names are no longer subject to validation checks.
    1262abf7
    History
    Remove tag_name_validator function and its usages
    Thorge Petersen authored
    The tag_name_validator function, which enforced restrictions on tag names, has been completely removed from the codebase. This change allows for unrestricted tag names, removing any validation based on the regular expression pattern. The decision to remove this function was made to align with the desired behavior of not imposing any limitations on tag names.
    
    This commit removes the tag_name_validator function and any code where it was called, ensuring that tag names are no longer subject to validation checks.