fluentsourcegen icon indicating copy to clipboard operation
fluentsourcegen copied to clipboard

Allows using C# source generators using a fluent, type safe interface rather than string templating.

Results 9 fluentsourcegen issues
Sort by recently updated
recently updated
newest added

## 🆙 Improvement proposal Ability to add attributes to properties. ## Context Add Attributes like **Required** , **Display** , **Length** , etc. Sometimes we need to add custom attributes.

enhancement

## 🆙 Improvement proposal Mark methods, fields, and properties as static.

enhancement
good first issue

## 🆙 Improvement proposal Make it possible to specify classes as partial. ## Context It is very common for source generators to expand on existing classes. In this case, the...

enhancement

## 🆙 Improvement proposal For MVP, we should have at least a way to manually specify the list of usings. ## Context Down the line, it would be cool if...

enhancement

## 🆙 Improvement proposal Classception. ## Context Might introduce some complexity when it comes to referring to it using its identifier.

enhancement

## 🆙 Improvement proposal Allow fields to be either mutable or readonly. ## Context Readonly should be the default.

enhancement
good first issue

## 🆙 Improvement proposal Allow implementation of properties, either with concrete getters and setters, or implicit ones. Getters and setters should also have the ability to have different visibility.

enhancement

## 🆙 Improvement proposal Right now we can only generate types in the root namespace. This is undesirable. ## Context Both namespace statements and namespace blocks should be allowed.

enhancement

## 🆙 Improvement proposal Right now the author of the source generator is required to populate a name for each field. If the author does not particularly care about the...

enhancement
good first issue