openlibhums / openlibhums/datacite
Move custom settings from plugin_settings.py to regular settings.py
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1
- Forks
- 1
- Avg merge
- 3m
- Merged PRs (30d)
- 1
Description
this plugin expects config to be provided through plugin_settings.py
Since this is a git tracked file, it gets in the way of applying plugin upgrades as it shows as a conflict whenever the file has had changes and could also lead to accidental data-loss while upgrading
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
Compare how configuration is currently loaded from plugin_settings.py with the regular settings.py entry point. Move the custom settings so upgrades no longer require changes to the tracked plugin_settings.py file, and verify that the plugin still receives its configuration without upgrade conflicts.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100