Exported: 2026-01-28 17:50:42
2026-01-28 18:03:44
| { | |
| "$id": "https://kubeflow.org/model-registry/catalog.yaml", | |
| "$schema": "https://json-schema.org/draft/2020-12/schema", | |
| "title": "Model Catalog", | |
| "type": "object", | |
| "properties": { | |
| "source": { | |
| "type": "string", | |
| "description": "The name of the catalog provider.", | |
| "example": "Red Hat" |
I just wanted to write down my thoughts about a possibly-naive but simple approach we could theoretically take to support PF4/PF5/Next component styles existing on the same page.
To be clear: I have not learned much about CSS layers or CSS modules, so this may be better achieved with something fancier. However, this would work without any browser compatibility concerns.
Proposal:
.pf-v-4 version classes on every component/layout style rule.
| #!/bin/sh | |
| minikube config set memory 10240 | |
| minikube config set cpus 4 | |
| minikube stop | |
| minikube delete | |
| minikube start --addons=dashboard --addons=ingress --addons=olm |
This is copied from https://unpkg.com/browse/@openshift-console/[email protected]/doc/console-extensions.md Pasted here to render the markdown for easier reference before it is published somewhere official.
Hi guys, let me know if there is a more appropriate channel for this but I figured we could have a place for async discussion around the Kogito PF stuff within UXD.
For those who want to set up and run the Kogito UI code locally, it's pretty simple. Here's how you can pull down the branches I've been working on with Ajay:
git clone https://github.com/kiegroup/kogito-apps
cd kogito-apps
git remote add mturley https://github.com/mturley/kogito-apps
git fetch mturley
git checkout KOGITO-new-tabledesign
Writing code for what we want the page to do, not how we want the browser to do it.
I've been working on how to try and explain the fundamental difference between the following two concepts of how programming the interactions on a web page can be done. It's important to grasp both in order to understand the main benefit of React from a developer's perspective. There are also design benefits of React such as the ability to reuse and compose isolated components, but that is beyond the scope of this document.
| #!/usr/bin/env bash | |
| pwd | |
| mkdir -p ./__tests__ | |
| for file in * | |
| do | |
| if test -f "$file" && [[ $file == *.js ]] | |
| then | |
| testfile="./__tests__/${file/\.js/.test.js}" | |
| if test -f "$testfile" |
| ERROR in /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-utils/dist/validateWithCustomRules.js | |
| Module not found: Error: Can't resolve 'graphql/validation/rules/ExecutableDefinitions' in '/Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/node_modules/graphql-language-service-utils/dist' | |
| @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-utils/dist/validateWithCustomRules.js 20:18-75 | |
| @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-utils/dist/index.js | |
| @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-interface/dist/getDefinition.js | |
| @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/graphql-language-service-interface/dist/index.js | |
| @ /Users/mturley/.rvm/gems/ruby-2.4.2/bundler/gems/manageiq-graphql-5f68621f2791/~/codemir |