saveourtool/save-cloud

EPIC: add the functionality of selecting Project Types for the new Project

Open

#753 opened on May 13, 2022

View on GitHub
 (1 comment) (0 reactions) (0 assignees)Kotlin (4 forks)github user discovery
enhancementgood first issuehelp wanted

Repository metrics

Stars
 (38 stars)
PR merge metrics
 (PR metrics pending)

Description

The idea is to add different types of tested tools to the SAVE eco-system. Right now we were focused on a standard static analysis. But we already get requests for compilers and Software Composition Analysis.

In this case we would like to add the following logic:

  • Each Project should have an entity TYPE - better it be a enum
  • This type should be propagated to BACKEND, DATABASE, ORCHESTRATOR, FRONTEND and (probably even agents)
  • Depending on the type - we will need to do different logic: for Static Analysis - it should be the same logic that we have now, but for SCA it can be a different logic on the frontend/backend/agents

Contributor guide

Research direction
Investigate the current project model and how it is used across backend, database, orchestrator, and frontend. Determine where to add the type enum and how to propagate it.
Tech stack
kotlin
Domain
backendfrontenddatabaseinfrastructure
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
3-5 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Mostly clear
Prerequisites
GitKotlin
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
50