Indexer: Rename index to createIndex#24075
Conversation
index to indexFnindex to indexFn
shilman
left a comment
There was a problem hiding this comment.
I don't love it, but I'm fine with it if that's the consensus.
What about indexFile instead? We generally don't use the Fn suffix in Storybook. For example, stories provide a render function instead of a renderFn, etc.
I agree about the I don't like Basically what we want to convey is "a function that takes in a file path and converts it to inputs to an index". Are any of these better you think?
Personally I like |
|
I don't have a strong opinion but I think @shilman is right that we generally use verbs not nouns for function names 🤷 So of these:
Only |
|
I could also go with |
index to indexFnindex to createIndex
Indexer: Rename `index` to `createIndex` (cherry picked from commit 9a2bc75)
What I did
This PR renames the
indexproperty on an indexer toindexFncreateIndexfor multiple reasons:indexis a very generic term that can mean a lot of things in different contexts.Checklist for Contributors
Testing
The changes in this PR are covered in the following automated tests:
Manual testing
This section is mandatory for all contributions. If you believe no manual test is necessary, please state so explicitly. Thanks!
Documentation
MIGRATION.MD
Checklist for Maintainers
When this PR is ready for testing, make sure to add
ci:normal,ci:mergedorci:dailyGH label to it to run a specific set of sandboxes. The particular set of sandboxes can be found incode/lib/cli/src/sandbox-templates.tsMake sure this PR contains one of the labels below:
Available labels
bug: Internal changes that fixes incorrect behavior.maintenance: User-facing maintenance tasks.dependencies: Upgrading (sometimes downgrading) dependencies.build: Internal-facing build tooling & test updates. Will not show up in release changelog.cleanup: Minor cleanup style change. Will not show up in release changelog.documentation: Documentation only changes. Will not show up in release changelog.feature request: Introducing a new feature.BREAKING CHANGE: Changes that break compatibility in some way with current major version.other: Changes that don't fit in the above categories.🦋 Canary release
This PR does not have a canary release associated. You can request a canary release of this pull request by mentioning the
@storybookjs/coreteam here.core team members can create a canary release here or locally with
gh workflow run --repo storybookjs/storybook canary-release-pr.yml --field pr=<PR_NUMBER>