OpenRefine / OpenRefine/sample-extension
Demonstrate how to avoid re-including theme.css
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 5
- Forks
- 11
- PR merge metrics
- No merged PRs in 30d
Description
Several extensions (https://github.com/OpenRefine/FilesExtension, https://github.com/OpenRefine/CommonsExtension) vendor the theme.css file to be able to style their own components accordingly. They should ideally be able to reuse it from the core application instead.
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 reviewing how this sample extension and the linked FilesExtension and CommonsExtension currently vendor theme.css. Identify the core application's reusable theme.css entry point and document or demonstrate its use in the sample extension. Done means the example shows extension components styled without maintaining a separate copy of theme.css.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100