Idea: Incorporate LcsApi library to the project
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 122
- Forks
- 58
- Avg merge
- 9d 3h
- Merged PRs (30d)
- 1
Description
Some months ago, I tried to standarize the API that is used in LCS based on the initial clients implemented in 2LCS. I ended up with this library. There are versions for .NET Framework and .NET Core 6 (not in sync), fully asynchronous, fully documented and with the following capabilities:
- Almost every environment (from Tier1 to prod) operations are supported
- Project settings
- Project methodologies
- Asset management (all operations)
- Sizing
- Diagnostics
Authentication through direct cookies and cookie capture (via Selenium) are supported.
The library comes with MIT license, so there is no problem with that :)
I think the project could potentially benefit from that implementation, being easier to maintain and expand, also allowing others to use it for automation purposes.
I can try to port it to this app myself, but I want to know if it is worth the efford. Thanks!
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
Start by reviewing the linked LcsApi library and the current 2LCS project to compare the .NET Framework and .NET Core 6 versions. Map the library’s supported operations and authentication approaches to what this app needs, then clarify the target integration scope and acceptance criteria before beginning implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- api, backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100