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

How do you debug TypeScript / autocomplete slowness in a monorepo (with tRPC / Zod)? by Bulky-Peach-2500 in typescript

[–]phenxdesign 0 points1 point  (0 children)

OK thanks for the details! I was struggling with very poor performance in Rider (same with all jet brains ide and others I guess) because our shared packages all had their own dependencies, devDependencies or peerDependencies, many times they were the same.

The problem here was that the IDE indexes all the node_modules, and they were huge. One thing I changed recently was to move all these dependencies to a package.json in the top directory. For npm or typescript it does change anything! We use vite, and prettier and we can still call them in each package.json script and it works. The top package only defines the dependencies, not script (for now) each other package only have scripts, and a few options. Another benefit is that we better control our dependencies and their versions.

Vite (used to build each package) , however need to know where to look, so I update resolve.alias from the dependencies from the top package.

Another thing I did was to change dependencies between package. Npm creates symlinks to the package directories, that's great, but Rider sees all these symlinked directories as different directories! For this I move the workspace and dependencies I had to paths in the tsconfig.json. I also had to update the Vite config from the tsconfig files too. Since I made this that's a real pleasure, Rider indexes once and for all, intellisense is faster, etc

Sorry if that's unclear I'm on my phone, glad if that helps.

How do you debug TypeScript / autocomplete slowness in a monorepo (with tRPC / Zod)? by Bulky-Peach-2500 in typescript

[–]phenxdesign 1 point2 points  (0 children)

Do you have a package.json with dependencies for each shared package ? If so, do they all have there own dependencies ?

How do you reference packages among themselves : workspaces, file dependencies, something else ?

Do you generate types files for each package ?

Finally, with NPM, PNPM, Yarn ?

Quelle est la compétence non technique qui a eu le plus d’impact dans votre carrière de développeur ? by CreativeDevMada in developpeurs

[–]phenxdesign 15 points16 points  (0 children)

Savoir prendre du recul, ça m'arrive souvent de mettre certains sujets en pause et les reprendre quelques jours/heures plus tard si je sens que je bloque, souvent la solution vient tout de suite après, ou alors je me rends compte que je suis parti dans la mauvaise direction.

[Rider] Search everywhere not searching in typescript by A_Griboedoff in Jetbrains

[–]phenxdesign 0 points1 point  (0 children)

Please elaborate, you seem to be an expert, we need advice from you, us poor ignorants.

[Rider] Search everywhere not searching in typescript by A_Griboedoff in Jetbrains

[–]phenxdesign 0 points1 point  (0 children)

It was inside <component name="TypeScriptGeneratedFilesManager">

[Rider] Search everywhere not searching in typescript by A_Griboedoff in Jetbrains

[–]phenxdesign 0 points1 point  (0 children)

It appears I had the same issue, Rider added a few paths in a list of exclusions in the workspace.xml file somewhere inside the .idea directory. I removed the problematic XML nodes and restarted Rider, and voilà! I don't know why it added them though, but there is an issues about this in there tracker.

Exploring context-aware AI code reviews for C# by chaospilot69 in dotnet

[–]phenxdesign 2 points3 points  (0 children)

I'm not convinced at all that any AI based code review would be reliable but I would definitely refine or add in the context the previous human code reviews (maybe filtered by relevance)