FluentBoilerplate

KO | EN

gitlite — search

#javascript #python #react #android #rust #deep-learning #macos #nodejs #awesome #cli #kubernetes #ios #openai #mcp

FluentBoilerplate

(★ 8)

This package provides an easy and fluent way to write the boilerplate requirements, exception handling, connection, type mapping, and validation that your code may depend on in order to actually write the business logic you require.

FluentBoilerplate 최신버젼 다운로드

최종 버전 다운로드 (.zip)

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

FluentBoilerplate
=================

All official release information / released builds are located at https://www.nuget.org/packages/FluentBoilerplate/.

**This is a beta-quality work in progress. This means that things could break or behave in unexpected ways.**

That said, you're more than welcome to <a href="https://github.com/Norhaven/FluentBoilerplate/wiki/How-can-I-contribute%3F">report any bugs you may find, contribute, etc.</a>

Enjoy!

Getting Started
=================

- Build the source (or get a release from NuGet, if available)
- Reference the built assembly in your project

**Or**

- Use the latest free version of Linqpad, install the NuGet package. Comes with samples!

This is a quick overview of the primary functionality. If you would like more in-depth samples, I would highly suggest that you look at the Linqpad samples in ./DotNet/FluentBoilerplate/linqpad-samples for more information.

The Linqpad samples are easily usable through the latest free version of Linqpad (http://www.linqpad.net).

Once you've downloaded and installed Linqpad, run it and press F4 while in a query window. There will be a button towards the bottom labelled "Add NuGet". Click it.

You'll be able to see any NuGet packages that contain Linqpad samples. Among those is FluentBoilerplate. Installing the package will provide you with all of the samples. Enjoy!

The Simplest Example
=================

The only namespace you should care about is FluentBoilerplate. Add that to your file's using statements.

```C#
using FluentBoilerplate;
```

Everything is driven from an IBoilerplateContext implementation. You should get one.

```C#
var boilerplate = Boilerplate.New();
```

Doing something within the context is very simple. If you don't want to return a result, you may do this.

```C#
boilerplate.Do(context => /* Take some action */);
```

If you'd like to get a result back, you may do this instead.

```C#
boilerplate.Get<int>(context => /* Take some action that returns an integer */);
```

After you get a result, you may want to use it.

```C#
var text = boilerplate
              .Get<string>(context => /* Take some action that returns a string */)
              .Result;
```

So why is that useful? Those actions can have a contract defined that applies to them.

For example, it might be nice to handle an ArgumentException that might be thrown when doing the action. For this, we need to create a contract.

```C#
boilerplate
    .BeginContract()
         .Handles<ArgumentException>(ex => Console.WriteLine(ex.Message))
    .EndContract()
    .Do(context => /* Take some action */);
```

If your call to Do() throws an ArgumentException, it will now be caught and its message written to the console. Just like you would with a try/catch block, you can define any number of exception types and their handlers, and the order they're defined in matches the order in which they're handled.

Contract Examples
=================

You may be saying to yourself "Self, this sounds sort of like Code Contracts", and you wouldn't be wrong. This follows along the same lines, in that it's very often ideal to be able to express pre and post conditions for a given action.

Let's require that a parameter is not null before we do something.

```C#
public static void DoSomething(IBoilerplateContext boilerplate, string text)
{
    boilerplate
        .BeginContract()
             .Require(() => text != null, "The parameter 'text' must not be null")
        .EndContract()
        .Do(context => /* Take some action */);
}
```

When the call to Do() is performed, the contract will be validated. If the parameter is null, a ContractViolationException will be thrown with the given message.

You're welcome to throw your own exceptions as well.

```C#
public static void DoSomething(IBoilerplateContext boilerplate, string text)
{
    boilerplate
        .BeginContract()
             .Require(() => text != null, () => new ArgumentException("text", "The parameter must not be null"))
        .EndContract()
        .Do(context => /* Take some action */);
}
```

Preconditions, like the ones above, are useful because you can verify that things are in a necessary state before you operate on it. Postconditions, on the other hand, are useful for ensuring that _you_ aren't leaving things in a bad state for anyone else.

Let's make sure that we're leaving the state appropriately.

```C#
public class Example
{
    public string Text { get; private set; }

public void DoSomething(IBoilerplateContext boilerplate)
    {
        boilerplate
            .BeginContract()
                .EnsureOnReturn(() => this.Text != null, "Text must be non-null on return")
                .EnsureOnThrow(() => this.Text == null, "Text must be null when an exception is thrown")
            .EndContract()
            .Do(context => /* Take some action */);
    }
}
```

There are two kinds of postconditions.

- EnsureOnReturn() makes sure that the state is appropriate when returning from the action. 
- EnsureOnThrow() makes sure that the state is appropriate when the action threw an exception.

Permissions
=================

You might want to be a little more specific in terms of what a particular caller is allowed or restricted from doing.

Let's say we have several rights that a given caller may or may not have.

```C#
public static class KnownRights
{
    public static IRight CanPerformAction = new Right(1, "User can perform an action");
    public static IRight CanDoTerribleThings = new Right(2, "User can do terrible things");
}
```

We'd like to make sure that the caller is allowed to perform an action, but not do anything terrible.

```C#
private void DoSomething(IBoilerplateContext boilerplate)
{
    boilerplate
        .BeginContract()
            .RequireRights(KnownRights.CanPerformAction)
            .MustNotHaveRights(KnownRights.CanDoTerribleThings)
        .EndContract()
        .Do(context => { /* Take some action */ });
}
```

You can also do the same thing at a roles level. Here are some arbitrary roles that we've just defined.

```C#
public static class KnownRoles
{
    public static IRole BasicUser = new Role(1,
                                             "A user",
                                             new HashSet<IRight>
                                             {
                                                 KnownRights.CanPerformAction
                                             }.ToImmutableHashSet());

public static IRole RestrictedUser = new Role(2,
                                                  "A user with limited access",
                                                  new HashSet<IRight>().ToImmutableHashSet());
}
```

You could then include roles in your contract.

```C#
private void DoSomething(IBoilerplateContext boilerplate)
{
    boilerplate
        .BeginContract()
            .RequireRoles(KnownRoles.BasicUser)
            .MustNotHaveRoles(KnownRoles.RestrictedUser)
        .EndContract()
        .Do(context => { /* Take some action */ });
}
```

How do we know what rights/roles the caller has, though?

When you create a context, one of the parameters you may optionally specify is an IIdentity instance. This represents the current caller that the context will operate under, and includes sets of rights/roles that they are permitted and explicitly denied. You are welcome to use an instance of the Identity class, which implements IIdentity, or write your own.

Supported rights/roles currently come from manually created objects (as above) or Active Directory, with more planned.

Validation
=================

The contract also offers a slightly more targeted approach to preconditions, by validating that a specific instance meets all of its requirements (in particular, its properties).

There are currently four attributes that may be applied to properties for validation, with more planned.

```C#
public class SomeType
{
    [NotNull]
    [StringLength(Minimum=3, Maximum=10)]
    public string Text { get; }
	
	[IntegerRange(Minimum=3, Maximum=42)]
	public int Value { get; }
	
	[IsMatchFor(@"\d+\w+")]
	public string Description { get; }
}
```

The [NotNull] attribute does what it says. During validation, that property must not be null.

The [StringLength] attribute enforces length requirements on a string property. Minimum is the inclusive lower bounds, meaning that the string must be three or more characters in length. Maximum is the inclusive upper bounds, meaning that the string must be ten or less characters in length.

The [IntegerRange] attribute enforces value requirements on an integer property. Minimum is the inclusive lower bounds, meaning that the value must be three or more. Maximum is the inclusive upper bounds, meaning that the value must be forty-two or less. This validation can apply to non-floating point numeric properties (e.g. Int32, Int64).

The [IsMatchFor] attribute enforces value requirements on a string property. During validation, the value of the string must be a match for the provided regular expression.

Let's validate an instance of SomeType.

```C#
private void DoValidatedAction(IBoilerplateContext boilerplate, SomeType instance)
{
    boilerplate
        .BeginContract()
            .RequireValidInstanceOf(instance)
        .EndContract()
        .Do(context => { /* Take some action */ });
```

When the Do() method executes, the validation will be performed. Validation is a precondition and will run prior to the Do() method execution, but it will run after any other preconditions.

This gives us an execution path of:

- Rights/Roles validations
- Requirements preconditions
- Instance validations
- Do()
- Postconditions

Translation
=================

At some point in your program, you may want to treat an instance as another type. You could create a manual translation layer, or use reflection, but it would be nice if the context could just figure it out.

Let's say you have a few classes.

```C#
public class From
{
    public string Text { get; set; }
}

public class To
{
    public string Text { get; set; }
    public string Description { get; set; }
}
        
```

Translation is fairly easy.

```C#
public void DoSomething(IBoilerplateContext boilerplate, From fromInstance)
{
    fromInstance.Text = "Hello";
    var toInstance = boilerplate.Use(fromInstance).As<To>();
    
    Console.WriteLine(toInstance.Text); //Prints out "Hello"
}
```

The context will translate the properties based on the name and type of the property. If you would like to customize the translation mappings, use the [MapsTo] attribute on the specific properties.

Let's redo the From class with an explicit mapping.

```C#
public class From
{
    [MapsTo(typeof(To), "Description"]
    public string Text { get; set; }
}
```

Now let's change the method a little bit.

```C#
public void DoSomething(IBoilerplateContext boilerplate, From fromInstance)
{
    fromInstance.Text = "Hello";
    var toInstance = boilerplate.Use(fromInstance).As<To>();
    
    Console.WriteLine(toInstance.Description); //Prints out "Hello"
}
```

Provided Type Usage
=================

That sounds fancy, but it's just a way of injecting your own type provider into the boilerplate.

So what does that actually mean?

There are quite a few scenarios in which you'd like to make use of a factory (e.g. WCF services, data access). The boilerplate context will help you get access to those types through an ITypeProvider implementation.

Let's create a simple WCF type provider for an example service. Here's the contract.

```C#
[ServiceContract]
public interface IExampleService
{
	[OperationContract]
	bool GetValue();
}
```

First, we're going to need to deviate from the basic FluentBoilerplate namespace. I know, I'm shocked too.

```C#
using FluentBoilerplate.Providers.WCF;
```

Now we need to know how to contact the service. Let's use an endpoint and binding in code for this example (getting this from configuration is also supported).

```C#
var binding = new NetNamedPipeBinding();
var address = "net.pipe://localhost/FluentBoilerplateExampleService";
```

Let's make a type provider that can provide us with an open connection to that service.

```C#
var service = new WcfService<IExampleService>(binding, new EndpointAddress(address));
var wcfProvider = new WcfConnectionProvider(new [] { service });
```

And now let's make the boilerplate context aware that it can access that type.

```C#
var wcfAccessProvider = new TypeAccessProvider(wcfConnectionProvider);
```

That's it! Let's get a new boilerplate context and call the service.

```C#
var boilerplate = Boilerplate.New(accessProvider: wcfAccessProvider);

var result = boilerplate.Open<IExampleService>()
                        .AndGet<bool>((context, service) => service.GetValue())
		                .Result;
```

Currently, there are providers available for WCF and for ADO.Net, with more planned.
You are also welcome to write your own provider that implements FluentBoilerplate.Providers.ITypeProvider and/or type access provider that implements FluentBoilerplate.Providers.ITypeAccessProvider and send them in with your initial Boilerplate.New() call.

FluentBoilerplate

FluentBoilerplate 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

FluentBoilerplate

FluentBoilerplate 최신버젼 다운로드

오늘의 추천 프로젝트

Was this content helpful?

Recent Feedback

Download README