Skip to content

Closes #545 Add option for additional using statements in the entity#546

Open
ArnaudB88 wants to merge 2 commits into
loresoft:masterfrom
ArnaudB88:feature/545-AdditionalUsings
Open

Closes #545 Add option for additional using statements in the entity#546
ArnaudB88 wants to merge 2 commits into
loresoft:masterfrom
ArnaudB88:feature/545-AdditionalUsings

Conversation

@ArnaudB88

@ArnaudB88 ArnaudB88 commented Mar 22, 2024

Copy link
Copy Markdown

Resolves #545
Add an option to insert additional using statements in the generated entity classes.

YAML usage:

data:
  entity:
    baseClass: 'IEntityBase'
    additionalUsings: 'Company.Project.Domain.Interfaces'

Code generation result:

using System;
using System.Collections.Generic;
using Company.Project.Domain.Interfaces;

namespace Company.Project.Domain.Entities;

public partial class Project
    : IEntityBase
{
}

@github-actions

Copy link
Copy Markdown
Contributor

⏰ Stale Pull Request

No activity for 1 year. Will close in 45 days unless updated.
To keep open, push commits, comment, or remove the stale label.

@github-actions github-actions Bot added the stale label Jun 21, 2026
@gitguardian

gitguardian Bot commented Jun 23, 2026

Copy link
Copy Markdown

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

Since your pull request originates from a forked repository, GitGuardian is not able to associate the secrets uncovered with secret incidents on your GitGuardian dashboard.
Skipping this check run and merging your pull request will create secret incidents on your GitGuardian dashboard.

🔎 Detected hardcoded secret in your pull request
GitGuardian id GitGuardian status Secret Commit Filename
15735455 Triggered Generic Password bcd4f92 .github/workflows/dotnet.yml View secret
🛠 Guidelines to remediate hardcoded secrets
  1. Understand the implications of revoking this secret by investigating where it is used in your code.
  2. Replace and store your secret safely. Learn here the best practices.
  3. Revoke and rotate this secret.
  4. If possible, rewrite git history. Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data.

To avoid such incidents in the future consider


🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Feature] Add option to insert additional using statements for the entity

1 participant