Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Any plans to separate the fluent APIs into a standalone project? #41

Closed
1 of 2 tasks
1249993110 opened this issue Jun 16, 2023 · 2 comments
Closed
1 of 2 tasks
Assignees
Labels
feature New feature or request triage Investigation required

Comments

@1249993110
Copy link

Feature request type

Other

Is your feature request related to a problem?

Can Normal Builder and Fluent Builder be published projects to NuGet package separately as two projects? I think sometimes people just want to use Normal Builder.

Describe the solution you would like

Publish Normal Builder and Fluent Builder as standalone NuGet package.

Describe alternatives you have considered

No response

Pull Request

  • I would like to do a Pull Request

Code of Conduct

  • I agree to follow this project's Code of Conduct
@1249993110 1249993110 added feature New feature or request triage Investigation required labels Jun 16, 2023
@mishael-o mishael-o self-assigned this Jun 17, 2023
@mishael-o
Copy link
Owner

Hi @1249993110, thanks for the feedback. There is no plan to publish the Builder and Fluent Builder as separate NuGet packages, as this would be extra effort and work, and I don't think it is worth it.

You can ignore or not use the Fluent Builder if doesn't provide value to you, however, it beneficial for other users who use both, so they don't have to add an extra package.

@1249993110
Copy link
Author

Thank you very much for your reply, I understand.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request triage Investigation required
Projects
None yet
Development

No branches or pull requests

2 participants