forgejo/modules/indexer/issues
nachtjasmin 8ee4a7d658 chore: ensure consistent import aliasing for services and models (#10253)
To make sure that the code stays maintainable, I added the `importas` linter to ensure that the imports for models and services stay consistent.

I realised that this might be needed after finding some discrepancies between singular/plural naming, and, especially in the case of the `forgejo.org/services/context` package, multiple different aliases like `gitea_ctx`, `app_context` and `forgejo_context`. I decided for `app_context`, as that seems to be the most commonly used naming.

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/10253
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
Co-authored-by: nachtjasmin <nachtjasmin@posteo.de>
Co-committed-by: nachtjasmin <nachtjasmin@posteo.de>
2025-11-30 17:00:57 +01:00
..
bleve feat(issue-search): support query syntax (#9109) 2025-11-19 16:05:42 +01:00
db chore: ensure consistent import aliasing for services and models (#10253) 2025-11-30 17:00:57 +01:00
elasticsearch feat(issue-search): support query syntax (#9109) 2025-11-19 16:05:42 +01:00
internal feat(issue-search): support query syntax (#9109) 2025-11-19 16:05:42 +01:00
meilisearch feat(issue-search): support query syntax (#9109) 2025-11-19 16:05:42 +01:00
dboptions.go feat(issue-search): support query syntax (#9109) 2025-11-19 16:05:42 +01:00
indexer.go chore: ensure consistent import aliasing for services and models (#10253) 2025-11-30 17:00:57 +01:00
indexer_test.go feat(issue-search): support query syntax (#9109) 2025-11-19 16:05:42 +01:00
util.go chore: ensure consistent import aliasing for services and models (#10253) 2025-11-30 17:00:57 +01:00