Key Takeaways
a few good principles (not rules) for naming libraries:
a) signal abstraction level
b) avoid being too literal for it constrains evolution
c) pronounceable and spellable
d) prefer nouns over verbs because libraries are things not actions
e) metaphors beat descriptions
Consequently, I would avoid imports, ímport, impørt
"Ingest" feels like it is in a good direction.
Would be careful with:
- Loader (sometimes implies in-memory only)
- Fetcher (suggests network-only)
- Parser (too narrow)
To come up with other names I’d probably think about additional context. What is being imported, how is it being done? Can those concepts be spun into a name?
dataloader.loadAll
dataloader.open
dataloader.import
I've called this kind of thing load, initialize, get_all, and so on.
I may also call it something based on where the data is stored if that is important. For example from_csv.
I might also name it based on what it is for. For example load_config.
Whatever seems clearest, and fits best with how the project itself does things.
importers
Not affiliated with Hacker News or Y Combinator. We simply enrich the public API with analytics.