Why not React.DOM.svg instead of mui.SvgIcon?

[mikamaunula]

Why not React.DOM.svg instead of mui.SvgIcon?

[mikamaunula]

It would nice if MUI dependency could be removed. Maybe If you could make pull request of that update. It would be then merged.

It is also ok to refer to this repo if you want to do your own repo.

Thanks for interest.

[Cottin]

After doing some more research around react + svg I found https://github.com/jhamlet/svg-react-loader which solves my problem in a different way. It let's you use SVGs inline but is a bit more flexible in that you can download any .svg file to use. But it's kind of a different use-case than your repo and both have value!

I apologise but I think I'm too lazy to do a pull request but I'm guessing introducing an element prop and doing something like this should be enough to remove the MUI dependency:

var React = require('react');

var createClass = require('create-react-class');
                                   <------------ Removed MUI

var ActionAlarm = createClass({
  displayName: 'ActionAlarm',

  getDefaultProps: function() {
    return {element: React.DOM.svg}          <------------ normal svg as default
  },

  render: function render() {
    return React.createElement(
      this.props.element,          <------ using element here
      this.props,
      React.createElement('path', { d: 'M... 7z' })
    );
  }

});

module.exports = ActionAlarm;

Like so, it's up to the consumer to supply a mui.svg as the element prop if he/she wants to.

[suhasv95]

@Cottin You can take a look at https://github.com/suhasv1995/material-react-icons. With absolutely zero dependencies.