ucdavis / ucdavis/Purchasing

KFS validation errors

Open
#140 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
7
Forks
5
PR merge metrics
No merged PRs in 30d

Description

If the fks upload isn't successful, result.Success===false, we should parse the reasons to display to the user. I had a vendor with an invalid id

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by locating the KFS upload handling and the result.Success check mentioned in the issue. Trace the unsuccessful response to determine where validation reasons are available and where upload feedback is displayed; done means those reasons are parsed and shown to the user.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
backend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.