PACKAGE_FORM
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 102
- Forks
- 182
- PR merge metrics
- No merged PRs in 30d
Description
I am trying to add further functionality to the scheming extension and would thus require to provide a modified package_form template in my own extension.
However, it seems to be impossible to get CKAN to recognize any other package_form besides the one in the scheming extension when using it.
Could you provide an hint how to do it?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by tracing how CKAN and the scheming extension select the package_form template, then reproduce the issue with a separate extension. Done means a custom package_form template supplied by another extension is recognized instead of only the scheming template.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100