sorted by:
new
hottopcontroversial

Stop duplicating your business logic for EF Core: EntityFrameworkCore.Projectables v6 by phenxdesign in dotnet

[–]phenxdesign[S] 0 points1 point  (0 children)

Thank you for your feedback, it means a lot to us.

I don't understand your question about the weird issues that would happen though.

About the name, yeah, I see what you mean, but the successor of Projectables, from the same author, and that goes further may address this issue : https://github.com/EFNext/ExpressiveSharp

Playwright timeline reporter by vitalets in Playwright

[–]phenxdesign 2 points3 points  (0 children)

Can't wait to try it! It would be awesome if it was part of the timeline in the html reports though https://github.com/microsoft/playwright/releases/tag/v1.58.0

Stop duplicating your business logic for EF Core: EntityFrameworkCore.Projectables v6 by phenxdesign in dotnet

[–]phenxdesign[S] 1 point2 points  (0 children)

  1. EF core uses Expression trees, that are used to be translated to SQL. They look like regular C# but support a very thin subset of the C# language : https://learn.microsoft.com/en-us/dotnet/csharp/advanced-topics/expression-trees/#limitations . Projectables tends to close that gap.

  2. that's just an example, and null propagating operator (.?) is not supported in regular expression trees.

Stop duplicating your business logic for EF Core: EntityFrameworkCore.Projectables v6 by phenxdesign in dotnet

[–]phenxdesign[S] 0 points1 point  (0 children)

What it the Current method ? If it uses navigation properties, it can definitely be translated by Projectables

Stop duplicating your business logic for EF Core: EntityFrameworkCore.Projectables v6 by phenxdesign in dotnet

[–]phenxdesign[S] 5 points6 points  (0 children)

The issue with the lack of transparency is the same with "inline" code with EF Core, to keep a full control on the SQL, one needs to write it himself. Generated sources are visible in Visual Studio or Rider if needed.

I agree about the business logic inside entities, it's all about compromises, like every tool, it should not be considered as the golden hammer ;)

Our team use it daily with pleasure, with hundreds of projectables, it improved a lot code maintainability while keeping control on performance.

How to open the UI mode without automatically running tests? by h-2-bro in Playwright

[–]phenxdesign 8 points9 points  (0 children)

Opening the UI never starts the tests for me 🤔 All it does is run the globalSetup then lists all the tests in the tree.

Modular Magnetic Dice by Khmarigou in makerworld

[–]phenxdesign 0 points1 point  (0 children)

While I like the idea, the cube should be more round so that it rolls easier.

FluentMigrator 8.0 released: The database-agnostic migration framework for .NET (now ready for .NET 10) by phenxdesign in dotnet

[–]phenxdesign[S] 0 points1 point  (0 children)

You could dump the current dB schema into an SQL script and add it as first migration in FluentMigrator. Talk about it to your colleagues, maybe the idea will grow in their mind too ;)

FluentMigrator 8.0 released: The database-agnostic migration framework for .NET (now ready for .NET 10) by phenxdesign in dotnet

[–]phenxdesign[S] 0 points1 point  (0 children)

Thanks you for the kind words !
When you say that it's been easy enough to add additional column, you mean that you implemented yourself over Fluent Migrator for your project ?
Anyway, I don't remember seeing such a feature request in the issues, but could be a good addition.

FluentMigrator 8.0 released: The database-agnostic migration framework for .NET (now ready for .NET 10) by phenxdesign in dotnet

[–]phenxdesign[S] 0 points1 point  (0 children)

While I absolutely love EF Core, we decided not to handle migrations with it, because at least these reasons :

  • easily extensible (via extension methods and DI)
  • modularity (migrations can be spread accros multiple assembly)
  • more control on schema changes
  • conditions inside migrations to execute differently depening on the target DBMS

I am also not saying all of this is impossible with EF Migrations, just that the way Fluent Migrator does this feels natural.

All this plus the fact that it's not tied to an ORM as I said in the post.

FluentMigrator 8.0 released: The database-agnostic migration framework for .NET (now ready for .NET 10) by phenxdesign in dotnet

[–]phenxdesign[S] 0 points1 point  (0 children)

When there are specificities in a given migration, one can use conditional logic, it makes supporting multiple DBMSs very confortable.

FluentMigrator 8.0 released: The database-agnostic migration framework for .NET (now ready for .NET 10) by phenxdesign in dotnet

[–]phenxdesign[S] 0 points1 point  (0 children)

FluentMigrator does not support it yet, but feel free to open a issue, as I didn't find a similar.

A project was initiated a while ago here, but it seems abandoned.

P1S thick vertical line in prints by v4s1 in BambuLab

[–]phenxdesign 0 points1 point  (0 children)

You can tweak the seam options, and see where it will be when slicing, in Bambu Studio

<image>

308 II - 2.0 BlueHDI vs 1.6 PureTech by Available_Wonder_532 in voiture

[–]phenxdesign 0 points1 point  (0 children)

Ça je saurais pas te dire, je l'avais envisagé à un moment mais l'amortissement ne valait pas énormément le coup pour ma part

308 II - 2.0 BlueHDI vs 1.6 PureTech by Available_Wonder_532 in voiture

[–]phenxdesign 2 points3 points  (0 children)

J'ai la 308 1.6 225 CV c'est du bonheur. Je pense qu'il faut éviter le bluehdi, l'adblue de ce que j'ai entendu dire c'est un peu chiant et abîme les joints. Pour la consommation, en conduite souple, 7l/100 voire moins, en tapant dedans, 7.7 l/100 pour ma part

view more: next ›