V3 to V4 Migration Tool

[kkirsche]

Hey Guys,

I wanted to know if there was interest in me creating a tool to migrate projects from V3 to V4. I was thinking about building a ruby gem which would go through source files and (if a flag was provided) prompt the user would they like to change .XXX with .YYY. I understand that the alpha isn't the correct time to build this as there is a lot of churn and change at this time, but I wanted to see if there was interest by the core team in having something like this built to ease the transition / migration for users and increase adoption of V4.

Any feedback or thoughts you have on this would be greatly appreciated.

I believe this would help to address issues such as #17240 where there is concern about ecosystem and migrations.

I know it's possible as I did it for V2 -> V3 just never released it publicly and feel it would be pretty straight forward

[mdo]

Definitely intrigued. Would love to see something on a small one-off component example to see how it works in practice.

[kkirsche]

@mdo sounds good. I can put together a one off with a focused setup to convert one of the examples provided in the Getting Started > Examples section.

Do you have a specific example you'd like to see this made for? I was thinking doing it for: http://getbootstrap.com/examples/jumbotron/ though if you don't think that has enough content or diversity let me know what kind of example or component you'd like and I'll build a one off for that.

EDIT: made a repo here where I'll build a focused example once I hear what direction the team would like to see me to go in regards to proof of concept / example https://github.com/kkirsche/bootstrap_migrator

[mdo]

I think we'll skip on this for now @kkirsche. It'd be rad to see it done, but I can't promise you'd get the kind of help you might need from us should you pursue it. <3

[kkirsche]

@mdo no worries. I'll probably tackle it anyway once the API stabilizes just as a proof of concept tool