Which is correct to use, @openshift/dynamic-plugin-sdk or @openshift-console/dynamic-plugin-sdk?

The OpenShift 4.12 docs here point to the openshift/console-plugin-template repo. That repo is using @openshift-console/dynamic-plugin-sdk.

I noticed that @openshift-console/dynamic-plugin-sdk is missing implementations of documented functions like k8sListResource, k8sCreateResource, etc. The types are there but the implementation isn't. Those functions are implemented in this repo though.

The documentation for the new modal dialogs show them being called with generics however the dynamic SDK doesn't actually export them with generics as far as I can tell. For example the dynamic SDK reference page shows the following example for useLabelModels:

const PodLabelsButton = ({ pod }) => {
  const { t } = useTranslation();
  const launchLabelsModal = useLabelsModal<PodKind>(pod);
  return <button onClick={launchLabelsModal}>{t('Edit Pod Labels')}</button>
}

https://docs.openshift.com/container-platform/4.14/web_console/dynamic-plugin/dynamic-plugins-reference.html

Trying to call the function with a generic results in a compilation failure with the error:

TS2558: Expected 0 type arguments, but got 1.

The useDeleteModal does actually need to support generics since AFAIK it uses the type to determine whether non-cascading deletes are supported and shows a checkbox to enable this.

@florkbr Is is possible at all to filter by annotation instead of only label in k8sListResource?

In Openshift, default storage class is only marked and handled via an annotation, so getting the default one out of many is a pain currently without helper tools like jq or node-jq https://www.baeldung.com/linux/kubernetes-labels-annotations

Background: Red Hat Open Data Hub odh-dashboard is using this library here for interactions with the openshift API.

When I'm developing a remote plugin, I want to enable webpack HMR feature, but when I edit the codes, an error will be emitted:

ERROR in [entry] [initial] dp-remote-starter.d4404b9346b30617fed9.hot-update.js
Missing call to __load_plugin_entry__

So I have to disable HMR for now, is that possible to support HMR?

We are using the dynamic plugin sdk to develop a self-provisioning ui for amq broker. In this, we are using storybook(https://storybook.js.org/) to ease the development of the UI. While trying to build the storybook components, the following error is seen

ERR! ModuleNotFoundError: Module not found: Error: Can't resolve '@console/dynamic-plugin-sdk/src/perspective/useActivePerspective' in '/Users/ajay/Work/KIE/activemq-artemis-self-provisioning-plugin/node_modules/@openshift-console/dynamic-plugin-sdk/lib/api'
ERR!     at /Users/ajay/Work/KIE/activemq-artemis-self-provisioning-plugin/node_modules/webpack/lib/Compilation.js:2016:28
ERR!     at /Users/ajay/Work/KIE/activemq-artemis-self-provisioning-plugin/node_modules/webpack/lib/NormalModuleFactory.js:798:13

Any help is much appreciated! Thanks in advance

The PF versions in dynamic-plugin-sdk are causing conflicting dependency issues in the v5 migration for various products such as OCP and ODH, cc @nicolethoen .

I am currently working on upgrading dynamic-plugin-sdk to PFv5 and adding the corresponding PF-related code changes.

Since we are renaming a lot of extension types and we allow only prefix core. we should write an eslint rule to check for the value.

As suggested here #29 (comment)