1.0.0-rc.2 Release candidate

[geromegrignon]

The new release candidate version towards v1 is out.

Changes are still about the migration from PrimeNG to Optimus UI:

• CSS layer not updated in the configuration
• some repos not merged into the @openng namespace
• migration schematic separated from ng add

[geromegrignon]

@Kermit @klafbang @gianluca-moro @Phong6698 @jeroenpol Could you give it a try?

It does not include Module Federation migration, we'll add a specific step on the documentation website.
If everything is fine, we'll quickly release v1, i'm currently working on last changes and updates on the website.

[jeroenpol]

Ran the schematic (npx nx add @openng/optimus-ui@1.0.0-rc.2) and the migration (nx g @openng/optimus-ui:migrate-from-primeng).

It worked flawlessly again. No build errors and a quick visual check also spotted no errors. I've also run our Playwright e2e test suite (few hunderd tests across ~4 apps), and that also succeeded.

No blockers from my end :)

[Phong6698]

I ran the migration schematic.

The only issue I had was @import 'tailwindcss-primeui'; in tailwind.css not being replaced with @import '@openng/optimus-ui-tailwindcss';.

Otherwise it looks good to me. Thanks again!

[gianluca-moro]

I have the same issue as @Phong6698 with the tailwind import not being replaced. Otherwise, it works without issues.

[gianluca-moro]

I also noticed the following thing to take into account:

I have the following CSS Layers configured in the providePrimeNG:

providePrimeNG({
  theme: {
    preset: PrimeNgThemePreset,
    options: {
      cssLayer: {
        name: 'primeng',
        order: 'theme, base, primeng, primeng-overwrites',
      },
      darkModeSelector: '.DARK',
    },
  },
})

And I have a primeng-overwrites.scss file with the following layer:

@layer primeng-overwrites { ... }

After the migration, it changed the layers in the config but did not adjust the layer name in the scss declaration. More precisely, after the migration it was like:

provideOptimus({
  theme: {
    preset: PrimeNgThemePreset,
    options: {
      cssLayer: {
        name: 'optimus',
        order: 'theme, base, optimus, optimus-overwrites',
      },
      darkModeSelector: '.DARK',
    },
  },
})

Notice that it's now called optimus-overwrites.
However, it did not change the layer declaration in primeng-overwrites.scss. After the migration, it was still:

@layer primeng-overwrites { ... }

[git-LennardRottjers]

Hey all,
I have followed the migration and have the following feedback:

1. https://optimus.openng.org/installation mentions to skip this page and use the migration guide if you already have primeng, but having that hyperlink to the actual guide would be nice.
2. Running the migration basically ends with a lot of update statements, however way higher in the logs there are a lot of warnings that parts could not be migrated automatically. (2b. It does not mention why). I recommend adding a message to the end of the logs clarifying that you should look for the warnings up top and resolve them. The migration guide does mention you should look for those messages, however I think it doesn't hurt to repeat it in the console itself.

3. A lot of the warnings seem to be "simple" imports so I would have expected those to be possible to migrate. Actually those are all code coverage files those files are in the .gitignore so maybe honor that?

Aside from this nitpick feedback the release seems stable to me. Thank you all for the hard work.