Add blueDarkAlt theme deprecation notice for v6.0.0

[daileytj]

Fixes PXBLUE-2453.

Changes proposed in this Pull Request:

• Add blueDarkAlt theme deprecation notice for v6.0.0

Additional Context

• According to https://jsdoc.app/tags-deprecated.html, you can include some text that describes more about the deprecation, but I wasn't able to get that appearing in the IntelliSense popup.

This is what it looks like if you try to import the darkThemeAlt theme into a project.

[jeffvg]

I've seen other depreciations also note the replacement of the named import. Should we do this as well?

[daileytj]

I've seen other depreciations also note the replacement of the named import. Should we do this as well?

There's not really a "replacement" import per se. They would now just exclusively use the blueDark theme and potentially our new wrapper components, depending on the use case.

[joebochill]

So I assumed that the AltThemeProvider was in this repo, but it looks like it’s local to the auth workflow. We will probably want to add a deprecation warning there too.

[joebochill]

You may want to throw a console.warn in this file so that users will actually get a warning in the log (not just intellisense on hover). I think if you just drop it above the definition for the alt theme it should spit out the warning if anybody imports anything from that file.

[jeffvg]

I've seen other depreciations also note the replacement of the named import. Should we do this as well?

There's not really a "replacement" import per se. They would now just exclusively use the blueDark theme and potentially our new wrapper components, depending on the use case.

guess we could call out the updated import in the dep comment? use blueDark

Like the testing I was doing last week with Angular the 'get.testBed' was deprecated and it had a comment.. just an idea not a big deal

[jeffvg]

this is another example

[daileytj]

I added the console.warn notice, but the additional jsdoc text is still not showing as an intellisense popup.

[jeffvg]

yeah weird it doesn't show. I'm not familiar with this but is the @see still something that's used? I set it in my local d.ts file.

Do we have control on the quick fix link above? right now the quick fix is just remove the import (can it be change import to blueDark instead?

[daileytj]

@jeffvg that @see thing isn't showing either. I can't see a way to configure the quick-fix options either, but that would be a nice feature. Is the deprecation message showing up for you? Just wondering if this is a local problem for me...

[jeffvg]

@jeffvg that @see thing isn't showing either. I can't see a way to configure the quick-fix options either, but that would be a nice feature. Is the deprecation message showing up for you? Just wondering if this is a local problem for me...

for me I see this when I hover over the striked through import name.. (the @see is here on my local)

[jeffvg]

ok this makes sense. Projects using ^5.1.0 of the theme would see the warning and depreciation info.