societe-generale / societe-generale/github-crawler
why do we check for exclusion in fetchIndicatorsValues ?
Nobody has claimed this yet.
- Dominant language
- Kotlin
- Stars
- 111
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
Summary
check why this https://github.com/societe-generale/github-crawler/blob/572c25f6d50ebd93de91f56784268fe99c432a78/github-crawler-core/src/main/kotlin/com/societegenerale/githubcrawler/RepositoryEnricher.kt#L62-L65
is necessary - looks like it should be managed earlier in the processing flow
Type of Issue
It is a :
- request
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 at RepositoryEnricher.kt lines 62-65 and trace the processing flow around fetchIndicatorsValues to understand why exclusions are checked there. Determine whether the check belongs earlier, then validate the agreed behavior with the existing test suite; the issue does not name a specific test or expected implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kotlin
- Domain
- backend
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100