sassoftware / sassoftware/pyviyatools
Suggestion: Validation Type: Report Validation
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 50
- Forks
- 42
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
considering how many reports can an organization have, to have a tool to validate the report themselves (if they load, if any object or data is not loaded, if there is any broken reference to the data, etc) in a folder, or recursively from a folder, or just all the reports, could be interesting and could provide much more information from SAS point of view than any external monitoring tool.
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
The issue names no files, tests, or entry point; begin by surveying the Python CLI tools that call SAS Viya REST APIs for existing report-related commands. Before implementation, clarify supported report scopes, validation checks, output, and acceptance criteria, since the issue currently does not define what completion looks like.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- api, cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100