Expose our DDF renderer and constants as an alias for other engines

[skateman]

We have our own renderer for DDF and it would be nice to expose it for other rails engines. This would allow me to continue in getting rid of final-form components in some provider repos by replacing them with DDF.

The alias is set to @@ddf, so we could load a component like this:

import MiqFormRenderer, { componentTypes, validatorTypes } from "@@ddf";

@miq-bot add_label enhancement, react
@miq-bot assign @himdel

[skateman]

This would still require the provider plugins to depend directly on DDF, which we might want to avoid if we'd like to avoid problems when upgrading DDF to newer versions. However, the only thing we need from DDF are constants, like componentTypes and validatorTypes so I could just export them from the app/javascript/forms/data-driven-form.

I am also thinking about renaming the data-driven-form to something cleaner and we might just want to expose that one single file. What do you think @himdel?

[himdel]

Oh, nice, I had started something similar in #4966, but never finished making all the code use it.

I'm not sure we should use this in a plugin though. Tying a plugin to the exact structure of files in manageiq-ui-classic sounds brittle, I think plugins should only use the component registry.

(I'd still go with something shorter, @@ManageIQ is perhaps too long, I was originally thinking something like ~ui but that's probably problematic for sass.)

[skateman]

@@miq-ui?

[himdel]

what about just @@ddf

nobody will ever type MiQ with the right capitalization

[himdel]

And you may need a similar entry in jest.config.js - moduleNameMapper section

[skateman]

Updated

[miq-bot]

Checked commit skateman@5d870bf with ruby 2.5.7, rubocop 0.69.0, haml-lint 0.28.0, and yamllint
0 files checked, 0 offenses detected
Everything looks fine. ⭐

[skateman]

@himdel are you okay with these changes now?

[himdel]

Sorry, LGTM :)