Skip to content

Move components from *ui-components #6716

@himdel

Description

@himdel

Current state:

ManageIQ/ui-components:

  • uses release branches (gaprindashvili, hammer, ivanchuk, master), corresponding to 0.9 (bower), 1.0, 1.1 and 1.2 npm releases
  • no automatic releases (I tried)
  • typical bugfix means 3-7 PRs now (bugfix, update ui-classic master, update ui-service master, and then 2 PRs per backport), and I can only review the first one, because I'm creating the others (https://github.com/himdel/dotfiles/tree/master/ManageIQ)
  • especially in the cases of dialog-user and dialog-editor, there is more logic in ui-classic and ui-service to complement the ui-components part, could be simplified by merging
  • originally meant to serve to share angular components between ui-classic and ui-service, but only miq-select and dialog-user are actually used in ui-service
  • uses a demo/ folder for examples

ManageIQ/react-ui-components:

  • no release branches (the first need to backport something without all the rest came in Make repeatedly searching through Tag Categories and Values work react-ui-components#167), thus no way to backport things
  • automatic releases
  • but a ui-classic PR still needs to happen to update the version (the only reason the PR count isn't the same is that we can't backport)
  • ui-classic is the only user of the repo
  • uses storybook for examples (and a demo/ folder)

New state:

Any ui-components component used exclusively by SUI will be moved to SUI:

Any ui-components component used exclusively by ui-classic will be moved to ui-classic:

Any react-ui-components used exclusively by ui-classic will be moved to ui-classic:

Unfinished react-ui-components work that should be finished at some point:

The rest of ui-components:

  • dialog-user - used by ui-classic and SUI, with almost-copies of the API talking code in the respective repos - merge with that, release as a separate package (or replace by new ddf-based dialog player, if relevant by then)
  • miq-select - release as part of the @pf/select (our existing fork of bootstrap-select, the jquery part of miq-select) (or possibly as part of bootstrap-select itself, which I'm now also a maintainer of)

Documentation:

We should merge the demo & storybook into one place documenting all our components, and add entires for the existing ui-classic ones.

(Currently not sure whether to go with storybook, we don't use the knobs that much, and it comes at the cost of a third separate webpack configuration (in addition to jest).)

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    Status

    To do

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions