microsoft / microsoft/api-guidelines
Naming convention for bulk operations?
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 23.3k
- Forks
- 2.7k
- PR merge metrics
- No merged PRs in 30d
Description
Are there any naming convention for bulk operations? The best one I found on a Google search is here, which seems good.
But I would adopt things published by Microsoft with more confidence.
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
No files, tests, or entry points are named. Start by reviewing the repository's existing API guideline documents and the linked bulk-operations naming guide, then determine whether Microsoft has an applicable published convention. Done would require an agreed naming convention to be documented, but this issue does not establish that decision.
Written by the indexing model from the issue text.
Assessment
- Domain
- api
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100