Steps to Reproduce

• Add an attribute that has a name and field/index type
  
• Clear the name
  

Expected

Field/Index Type should remain in their respective fields

Actual

Field/Index Type "shifts" into the name field

Add a new attribute, select field type without entering name. Filed type is not set, instead name is set as field type.

https://rails.help provides wrong example:

bin/rails g model ExampleModel other_model:references{polymorphic}:uniq lng:decimal{10,6}

right example:

bin/rails g model ExampleModel other_model:references{polymorphic}:uniq lng:decimal{10-6}

Please change decimal{10,6} to decimal{10-6}

Ideally break into smaller PRs. Some discussion can be found at #4 (comment) - the proposed is to have the individual FieldInputs (could we rename to AttributeForm?) do the validation and only call onUpdate if the inputs are valid (sort of an uncontrolled component). I think we don't need to show an error in the command UI at this moment, just the form inputs.

We can follow https://tailwindui.com/components/application-ui/forms/input-groups#component-7a5297f99a5ed22df80939dd1986de5f, example HTML / classes:

<!--
  This example requires Tailwind CSS v2.0+ 
  
  This example requires some changes to your config:
  
  // tailwind.config.js
  module.exports = {
    // ...
    plugins: [
      // ...
      require('@tailwindcss/forms'),
    ]
  }
-->
<div>
  <label for="email" class="block text-sm font-medium text-gray-700">Email</label>
  <div class="mt-1 relative rounded-md shadow-sm">
    <input type="text" name="email" id="email" class="block w-full pr-10 border-red-300 text-red-900 placeholder-red-300 focus:outline-none focus:ring-red-500 focus:border-red-500 sm:text-sm rounded-md" placeholder="[email protected]" value="adamwathan" aria-invalid="true" aria-describedby="email-error">
    <div class="absolute inset-y-0 right-0 pr-3 flex items-center pointer-events-none">
      <!-- Heroicon name: solid/exclamation-circle -->
      <svg class="h-5 w-5 text-red-500" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 20 20" fill="currentColor" aria-hidden="true">
        <path fill-rule="evenodd" d="M18 10a8 8 0 11-16 0 8 8 0 0116 0zm-7 4a1 1 0 11-2 0 1 1 0 012 0zm-1-9a1 1 0 00-1 1v4a1 1 0 102 0V6a1 1 0 00-1-1z" clip-rule="evenodd" />
      </svg>
    </div>
  </div>
  <p class="mt-2 text-sm text-red-600" id="email-error">Your password must be less than 4 characters.</p>
</div>

Model Generator

• model name should be CamelCased or under_scored only
• attribute name is required
• does attribute name need to be under_scored?
• field type is required
• limit / precision / scale modifiers should be positive integers only
• reserved attribute names e.g. type is used for single table inheritance

Currently, on refresh one will lose data.

Ability to save generators to local storage can help solve

1. Keep a history of commands, edit older commands.
2. Persist data on refresh.

Feature Request

Users can generate and share URL on guiderails.
e.g. https://guiderails.wasabigeek.com/?gen=bin/rails|g|model|ExampleModel|other_model:references{polymorphic}:uniq

GUI loads with given data in URL

Like a playground for rails generator.

• Move model generator to it's own page
• Users can find a generator by use case (e.g. "create a new model", "add attributes to an existing model")
• Users can find a generator by command (e.g. "rails g model", "rails g migration")

Dependency #7

The main README file contains a broken link to a file named USAGE which does not exist.

Slightly ambitious, should be interesting. Rough approach:

• Parse the generator classes (probably best to use something like https://github.com/rubocop/rubocop-ast / https://github.com/whitequark/parser, so yes, we'll probably add Ruby here)
• Output generator React files (at least a starter template. Since we add Ruby previously, may as well use thor)

Example generator classes:

• https://github.com/rails/rails/blob/main/railties/lib/rails/generators/rails/model/model_generator.rb
• https://github.com/rails/rails/blob/main/railties/lib/rails/generators/rails/controller/controller_generator.rb
• https://github.com/rails/rails/blob/main/railties/lib/rails/generators/rails/migration/migration_generator.rb

We should be able to extract the argument and class_options and generate some generic components in React. There will be some that we want special logic (e.g. in [migrations](- https://github.com/rails/rails/blob/main/railties/lib/rails/generators/rails/migration/migration_generator.rb
) there is an argument: :attributes, type: :array... which we could use to insert the AttributeArguments component) but those can be edited manually.

There's also some intricacy to how some generators hook into others, which I haven't quite figured out yet e.g. there's a lot more logic relating to the model/migration's attributes. I'm guessing it invokes the ActiveRecord Model Generator)