Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Do not auto-register prefixed resource blueprint;#7374

Merged
wardi merged 5 commits into
ckan:masterfrom
JVickery-TBS:fix/resource-auto-register-blueprint
Feb 2, 2023
Merged

Do not auto-register prefixed resource blueprint;#7374
wardi merged 5 commits into
ckan:masterfrom
JVickery-TBS:fix/resource-auto-register-blueprint

Conversation

@JVickery-TBS
Copy link
Copy Markdown
Contributor

Fixes

The prefixed_resource blueprint by the name of resource needs auto register False to allow for proper blueprint overrides.

Proposed fixes:

Set prefixed_resource.auto_register = False

Features:

  • includes tests covering changes
  • includes updated documentation
  • includes user-visible changes
  • includes API changes
  • includes bugfix for possible backport

Please [X] all the boxes above that apply

@wardi wardi self-assigned this Feb 2, 2023
@JVickery-TBS
Copy link
Copy Markdown
Contributor Author

@wardi As discussed, prefixed_resource will not be auto-loaded with the core blueprints. It will NOW get loaded at the very end of the register_package_blueprints method.

This should allow for the <package_type>_resource blueprints to take priority over the resource blueprints. This should solve issues with overriding the <package_type>_resource blueprints.

Comment thread ckan/tests/lib/test_helpers.py
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants