Merge pull request #1 from synboxdev/Development

Project

Author: synboxdev

CODE_OF_CONDUCT.md

@@ -0,0 +1,131 @@
+# Code of Conduct
+
+## Our Pledge
+
+We as members, contributors, and leaders pledge to make participation in our
+community a harassment-free experience for everyone, regardless of age, body
+size, visible or invisible disability, ethnicity, sex characteristics, gender
+identity and expression, level of experience, education, socio-economic status,
+nationality, personal appearance, race, caste, color, religion, or sexual
+identity and orientation.
+
+We pledge to act and interact in ways that contribute to an open, welcoming,
+diverse, inclusive, and healthy community.
+
+## Our Standards
+
+Examples of behavior that contributes to a positive environment for our
+community include:
+
+* Demonstrating empathy and kindness toward other people
+* Being respectful of differing opinions, viewpoints, and experiences
+* Giving and gracefully accepting constructive feedback
+* Accepting responsibility and apologizing to those affected by our mistakes,
+  and learning from the experience
+* Focusing on what is best not just for us as individuals, but for the overall
+  community
+
+Examples of unacceptable behavior include:
+
+* The use of sexualized language or imagery, and sexual attention or advances of
+  any kind
+* Trolling, insulting or derogatory comments, and personal or political attacks
+* Public or private harassment
+* Publishing others' private information, such as a physical or email address,
+  without their explicit permission
+* Other conduct which could reasonably be considered inappropriate in a
+  professional setting
+
+## Enforcement Responsibilities
+
+Community leaders are responsible for clarifying and enforcing our standards of
+acceptable behavior and will take appropriate and fair corrective action in
+response to any behavior that they deem inappropriate, threatening, offensive,
+or harmful.
+
+Community leaders have the right and responsibility to remove, edit, or reject
+comments, commits, code, wiki edits, issues, and other contributions that are
+not aligned to this Code of Conduct, and will communicate reasons for moderation
+decisions when appropriate.
+
+## Scope
+
+This Code of Conduct applies within all community spaces, and also applies when
+an individual is officially representing the community in public spaces.
+Examples of representing our community include using an official e-mail address,
+posting via an official social media account, or acting as an appointed
+representative at an online or offline event.
+
+## Enforcement
+
+Instances of abusive, harassing, or otherwise unacceptable behavior may be
+reported to the community leaders responsible for enforcement.
+All complaints will be reviewed and investigated promptly and fairly.
+
+All community leaders are obligated to respect the privacy and security of the
+reporter of any incident.
+
+## Enforcement Guidelines
+
+Community leaders will follow these Community Impact Guidelines in determining
+the consequences for any action they deem in violation of this Code of Conduct:
+
+### 1. Correction
+
+**Community Impact**: Use of inappropriate language or other behavior deemed
+unprofessional or unwelcome in the community.
+
+**Consequence**: A private, written warning from community leaders, providing
+clarity around the nature of the violation and an explanation of why the
+behavior was inappropriate. A public apology may be requested.
+
+### 2. Warning
+
+**Community Impact**: A violation through a single incident or series of
+actions.
+
+**Consequence**: A warning with consequences for continued behavior. No
+interaction with the people involved, including unsolicited interaction with
+those enforcing the Code of Conduct, for a specified period of time. This
+includes avoiding interactions in community spaces as well as external channels
+like social media. Violating these terms may lead to a temporary or permanent
+ban.
+
+### 3. Temporary Ban
+
+**Community Impact**: A serious violation of community standards, including
+sustained inappropriate behavior.
+
+**Consequence**: A temporary ban from any sort of interaction or public
+communication with the community for a specified period of time. No public or
+private interaction with the people involved, including unsolicited interaction
+with those enforcing the Code of Conduct, is allowed during this period.
+Violating these terms may lead to a permanent ban.
+
+### 4. Permanent Ban
+
+**Community Impact**: Demonstrating a pattern of violation of community
+standards, including sustained inappropriate behavior, harassment of an
+individual, or aggression toward or disparagement of classes of individuals.
+
+**Consequence**: A permanent ban from any sort of public interaction within the
+community.
+
+## Attribution
+
+This Code of Conduct is adapted from the [Contributor Covenant][homepage],
+version 2.1, available at
+[https://www.contributor-covenant.org/version/2/1/code_of_conduct.html][v2.1].
+
+Community Impact Guidelines were inspired by
+[Mozilla's code of conduct enforcement ladder][Mozilla CoC].
+
+For answers to common questions about this code of conduct, see the FAQ at
+[https://www.contributor-covenant.org/faq][FAQ]. Translations are available at
+[https://www.contributor-covenant.org/translations][translations].
+
+[homepage]: https://www.contributor-covenant.org
+[v2.1]: https://www.contributor-covenant.org/version/2/1/code_of_conduct.html
+[Mozilla CoC]: https://github.com/mozilla/diversity
+[FAQ]: https://www.contributor-covenant.org/faq
+[translations]: https://www.contributor-covenant.org/translations

CONTRIBUTING.md

@@ -0,0 +1,49 @@
+# Contributing to 'Collection of coding exercises'
+
+First and foremost, I appreciate you being interested enough in this project to even consider contributing to it as a whole. The following contents of the document lay out the basic rules and guidelines about contributing to the project. That being said, by no means these are laws set in stone - follow your best judgment, and feel free to propose changes to this document, or the project itself. Any and all positive contributions are always welcome, including features, issues, documentation, guides, and more.
+
+---
+
+## 📄 Table of contents
+
+* [Code of Conduct](#code-of-conduct)
+* [GitHub Terms of Service](#github-terms-of-service)
+* [Guidelines of contribution](#guidelines-of-contribution)
+    * [Code conventions](#code-conventions)
+    * [Issues](#issues)
+* [How to contribute](#how-to-contribute)
+
+---
+
+## Code of Conduct
+This project and everyone participating in it are governed by the [Code of Conduct](CODE_OF_CONDUCT.md). By participating and contributing the the project and its contents, you are expected to uphold this code.
+
+---
+
+## Github Terms of Service
+If it wasn't already clear - you should always follow [GitHub's terms of service](https://docs.github.com/en/site-policy/github-terms/github-terms-of-service) not only when contributing to this project, but to any and all repositories on the platform - follow the rules
+
+---
+
+## Guidelines of contribution
+
+## Code conventions
+In order for the project to remain well-built and structured you should align with stylistic of the code in the repo already. Good place to start would be following [Microsoft C# Coding Conventions](https://learn.microsoft.com/en-us/dotnet/csharp/fundamentals/coding-style/coding-conventions).
+
+---
+
+## Issues
+I'd consider [GitHub Issues](https://docs.github.com/en/issues/tracking-your-work-with-issues/about-issues) as a standardized and widely accepted way of contributing to the project and its contents. It covers everything from feature requests, bugs, suggestions to questions. If you wish to read further, GitHub documentation on [Creating an issue](https://docs.github.com/en/issues/tracking-your-work-with-issues/creating-an-issue) has got you covered. As a general rule of thumb, here's a few bullet-points I'd like you to follow, when creating an issues, regardless of its type:
+* Title of the issues should be clear, concise and descriptive.
+* Utilize existing [labels](https://docs.github.com/en/issues/using-labels-and-milestones-to-track-work/managing-labels) for your issues to be more informative. If you believe an additional label should be added - create an issue with a default label 'enhancement', where you'd explain what that new label should be, as well as provide reasoning as to why it should be added to the project.
+* Provide an informative, comprehensive description of the bug, suggested feature or an enhancement that you believe should be changed/added or improved in the project.
+* Feel free to provide pictures, flowcharts or any other forms of visual representation of the suggestion or a problem. Make it easy for others to understand you, and get on the same page.
+
+---
+
+## How to contribute
+1. Clone the repository and make a new branch. [README.md Getting started](README.md) section might be a good starting point.
+2. Make any and all changes to your branch. Whatever that might be - a bugfix, a feature or a documentation change.
+3. Do NOT clump together multiple things into the same branch - a single branch should cover a single thing.
+4. Make sure all projects build successfully and pass all the unit tests.
+5. [Create a pull request](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/creating-a-pull-request) with understandable, short and concise description of changes.

Dockerfile

@@ -0,0 +1,28 @@
+# Base stage
+FROM mcr.microsoft.com/dotnet/aspnet:9.0 AS base
+WORKDIR /app
+EXPOSE 8080
+EXPOSE 8081
+
+# Build stage
+FROM mcr.microsoft.com/dotnet/sdk:9.0 AS build
+ARG BUILD_CONFIGURATION=Release
+WORKDIR /src
+COPY ["Hestia.Api/Hestia.Api.csproj", "Hestia.Api/"]
+RUN dotnet restore "Hestia.Api/Hestia.Api.csproj"
+COPY . .
+WORKDIR "/src/Hestia.Api"
+RUN dotnet build "Hestia.Api.csproj" -c $BUILD_CONFIGURATION -o /app/build
+
+# Publish stage
+FROM build AS publish
+ARG BUILD_CONFIGURATION=Release
+RUN dotnet publish "Hestia.Api.csproj" -c $BUILD_CONFIGURATION -o /app/publish /p:UseAppHost=false
+
+# Final stage
+FROM base AS final
+WORKDIR /app
+COPY --from=publish /app/publish .
+EXPOSE 80
+EXPOSE 443
+ENTRYPOINT ["dotnet", "Hestia.Api.dll"]

Hestia.Access/Entities/Authentication/TokenLog.cs

@@ -0,0 +1,9 @@
+namespace Hestia.Access.Entities.Authentication;
+
+public class TokenLog(Guid id) : BaseEntity(id)
+{
+    public required string IdentityUserId { get; set; } = null!;
+    public required DateTime DateCreated { get; set; }
+    public required DateTime TokenExpirationDate { get; set; }
+    public required string Token { get; set; } = null!;
+}

Hestia.Access/Entities/BaseEntity.cs

@@ -0,0 +1,9 @@
+using System.ComponentModel.DataAnnotations;
+
+namespace Hestia.Access.Entities;
+
+public abstract class BaseEntity(Guid id)
+{
+    [Key]
+    public Guid Id { get; private set; } = id;
+}

Hestia.Access/Entities/Product/Product.cs

@@ -0,0 +1,13 @@
+namespace Hestia.Access.Entities.Product;
+
+public class Product(Guid id) : BaseEntity(id)
+{
+    public required string ExternalId { get; set; } = null!;
+    public required string UserId { get; set; } = null!;
+    public required DateTime DateCreated { get; set; }
+    public required string Name { get; set; } = null!;
+    public required string Description { get; set; } = null!;
+    public required decimal? Price { get; set; }
+
+    public DateTime DateEdited { get; set; }
+}

Hestia.Access/Entities/User/User.cs

@@ -0,0 +1,8 @@
+namespace Hestia.Access.Entities.User;
+
+public class User(Guid id) : BaseEntity(id)
+{
+    public required string IdentityUserId { get; set; } = null!;
+    public required DateTime DateCreated { get; set; }
+    public required string Name { get; set; }
+}

Hestia.Access/Hestia.Access.csproj

@@ -0,0 +1,17 @@
+<Project Sdk="Microsoft.NET.Sdk">
+
+  <PropertyGroup>
+    <TargetFramework>net9.0</TargetFramework>
+    <ImplicitUsings>enable</ImplicitUsings>
+    <Nullable>enable</Nullable>
+  </PropertyGroup>
+
+  <ItemGroup>
+    <PackageReference Include="MediatR" Version="12.4.1" />
+  </ItemGroup>
+
+  <ItemGroup>
+    <ProjectReference Include="..\Hestia.Domain\Hestia.Domain.csproj" />
+  </ItemGroup>
+
+</Project>

Hestia.Access/Requests/Authentication/Commands/CreateTokenLog/CreateOrUpdateTokenLogCommand.cs

@@ -0,0 +1,5 @@
+using MediatR;
+
+namespace Hestia.Access.Requests.Authentication.Commands.CreateTokenLog;
+
+public sealed record CreateOrUpdateTokenLogCommand(string Token, string IdentityUserId, DateTime TokenExpirationDate) : IRequest<Unit>;

Hestia.Access/Requests/Product/Commands/CreateProduct/CreateProductCommand.cs

@@ -0,0 +1,5 @@
+using MediatR;
+
+namespace Hestia.Access.Requests.Product.Commands.CreateProduct;
+
+public sealed record CreateProductCommand(Entities.Product.Product Product) : IRequest<bool>;