microsoft / microsoft/ConcordExtensibilitySamples
Breaking changes
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 135
- Forks
- 54
- Avg merge
- 5h 58m
- Merged PRs (30d)
- 3
Description
I am creating this issue as a place to announce breaking changes to the Concord API that might impact extension authors. To try and keep this to just announcements, I am going to lock this thread. But feel free to open issues in this repo if the instructions are unclear.
Contributor guide
No contributing guide indexed for this repository
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
Read the issue body first: it describes a locked announcement thread for Concord API breaking changes and does not identify a file, test, or implementation task. There is no newcomer-sized change or completion check specified; unclear instructions should be raised in a separate issue as requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100