hardenedelements / routable Goto Github PK

This project could definitely use some serious love in the unit test department.

If no model is provided, RenderContext crashes.

The new Sprache based parser drops . from the expression, making nested properties impossible.

Allow views to incorporate the content of other views. This may be accomplished by nesting the AST of the included view within the AST of the caller. Protip: the nested content will not expire properly when changes are detected unless written properly.

Feature request

Couple suggestions..

• Replace dependency on Newtonsoft.Json.Linq with .NET Core System.Text.Json.
• Remove the project.

Feature Request

Add support for pattern matching to determine if a value has a certain shape.

Proposed solution

Add an extension method with concise syntax like Add(route => route.Post().Pattern("/test/{id:guid}")

Additional context

Should support or handle uri with omitted forward slash

It seems the line endings throughout the project have become inconsistent. Use dos2unix and clean up the entire repository while it's young. This will dirty up git-blame.

Synopsis

Create a template package for use with dotnet new to help users get started with Routable.

A contribution guide will help others provide pull requests for the improvement of the project.

If view configuration were enumerable, a library author could offer a routing collection, extension method for adding the functionality of said library and leverage embedded views from the library assembly. All without interfering with the calling web application.

Add @foreach support to the template.
Acceptance Criteria Example

<ul>
  @ForEach.Users
  <li>@Model.Name</li>
  @EndForEach
</ul>

User should be able to obtain the root model regardless of nesting level (eg. within a @ForEach) using the @Root expression.

Using regular expressions for model value replacement is a quick and dirty method of providing a template engine. However, using Sprache we can have more advanced view template operations and we can add more easily.

Acceptance criteria

1. Use Sprache to parse view templates to a tree of operations.
2. Cache operation tree as in-memory representation of views.
3. Render operation trees against a model on demand.
4. Bonus, detect template updates and re-parse the view template.

If multiple routes match a given request, they should be enumerated individually and each one should be processed sequentially until one of the routes successfully processes the request in full. For example, if we have four routes, and the first two are bypassable routes that return false, the third will be processed - and if that route is successfully processed the fourth will not be.

Use case

• Authentication patterns
• Session management
• Authorization patterns
• Auditing
• Analytics

If one or more route add parameters with the same key, the value of the last parameter should be retained as the parameter of record.

The exception thrown by RoutableRequest.cs needs to be handled.

Currently the Routable.Views.Simple library resolves views using the file system. This should use a view resolution delegate with handy shortcuts for file system loading; and perhaps embedded resource streams.

This project is in desperate need of good documentation. Start by documenting this issue 😄