Why does api.content.create expect `type` instead of `portal_type`?
Open
Nobody has claimed this yet.
05 type: question
- Dominant language
- Python
- Stars
- 101
- Forks
- 62
- Avg merge
- 15h 15m
- Merged PRs (30d)
- 1
Description
This always throws me off because it is inconsistent. find and get expect portal_type. Could we at least add portal_type as another possible kwarg?
Contributor guide
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 with the api.content.create entry point and compare how api.content.find and api.content.get handle the portal_type keyword. Confirm the expected keyword behavior and add portal_type as an accepted alternative for create; done means callers can use portal_type consistently without breaking type.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100