Skip to content

Developers Experience

Jump to bottom
samatrhea edited this page Apr 28, 2024 · 3 revisions

We welcome contributions to the Kalliope Codebase, Please read the Contribution Guidelines. These explain how to make a Pull Request and the style Guidelines.

Tickets, Documentation and Code Review

GitHub is used as source repository, for ticketing to report issues, to plan work in sprints and to perform Code Reviews using GitHub PR's.

IDE

The core development team of the Kalliope makes use of Visual Studio 2022, the community edition can be downloaded here. We make use of Jetbrains Resharper Ultimate to make our developer lives easier. The solution contains a .DotSettings file that contains the core developer team's preferred Resharper code styles and formats.

In order to get started with Kalliope development, download VS2022 and open the .sln file to load all the projects.

Continuous Integration

GitHub actions are used to perform Continuous Integration:

  • CodeQL: semantic code analysis to find security vulnerabilities.
  • Build & Test & SonarQube: build, unit test/coverage, SonarQube Quality analysis

SonarQube Status:

Quality Gate Status Code Smells Coverage Duplicated Lines (%) Lines of Code Maintainability Rating Quality Gate Status Reliability Rating Security Rating Technical Debt Vulnerabilities

copyright @ Starion Group S.A.

Kalliope

  1. Home
  2. Documentation Overview
  3. Quick Start
  4. Roadmap

Soultion Structure

  1. Solution Structure

Kalliope Data Model

  1. The Data Model
  2. Kalliope Attributes
  3. Code Generation

Kalliope ORM to OO

  1. Intermediate OO classes

Code Generation with Kalliope

  1. Code Generation

Developer Environment

  1. Developers Experience
  2. Build and Release
Clone this wiki locally