In Bundle.php, We're creating Content types so it should reflect the naming. Please refactor the code to use ContentType instead of Bundle

Steps to reproduce

• Enable dst_entity_generate module
• Goto configuration page
• Try to upload a credentials.json file
• You will see an error.

Expected outcome:

• I should be able to upload a file without any error\

Possible solution:

• Check if private file path destination is set, if not throw an error.

1. There should be a warning/message for the user to go to the Google Sheet API tab to configure and come back.
2. As soon as you save the Google Sheet API, the user should be redirected to the General Tab.
3. After adding the Sheet API configurations successfully - the General tab still shows the empty with the specific creds: contact for creds.

This is a module, hence it should not compose.lock file.

• Create a common method service - E.g. GeneralApi
• Given an example on how to use it.

While exporting the configuration, the module should export the Google Sheet API tab configurations as well.

1. Remove Debug mode.
2. Code cleanup related to Debug mode.
3. As per new form settings, update skipEntitySync method.
4. Use skipEntitySync method in all command.
5. Create a common method to display message if sync is disabled.
6. Create a common method to display and log exception.
7. Code cleanup.

Change the service identifier dst_entity_generate.google_sheet to dst_entity_generate.google_sheet_api

Make sure to update wherever used.

We should use the CONST ENTITY_TYPE_MAPPING instead of adding this again here.

Originally posted by @vyasamit2007 in #89 (comment)

Prompt for enabling entity sync if respective entity sync is not enabled.

We can update existing commands to handle update mode.

Possible implementation approach:

1. Add new configuration item in form to set implementation status value. If row is updated after implementation, c will be the value in X column.
2. Currently we are filtering data by matching rows where w value is set in x column. This logic can be found in filterApprovedData function of BaseEntityGenerate class.
3. We need to grab content with value w as well as c. So, logic written in filterApprovedData function need to correct.
4. Create a new function in individual command to update respective entity type.
5. In original command execution, If we get a row with value c in x column and entity type is already exist,
   pass row to update function.
6. Update function will have predefined column list that we can consider to update entity type. E.g. Label, description.
7. Once entity type get updated, display message and return to original command execution.

Scope:

1. Update only entity types in first phase.
2. Updation of fields can be consider after we are able to update entity types.

Possible fields that can be consider to update entity type:
Content type

1. Name
2. Description
3. Mod.
4. Trns.
5. Cmnt.
6. URL alias pattern

User roles

1. Name

Workflows

1. Label

Workflow states

1. Label
2. Workflow(Need to check whether it is possible or not.)

Workflow transitions

1. Label
2. Workflow(Need to check whether it is possible or not.)
3. From state
4. To state

Menus

1. Title
2. Description

Image styles

1. Style name

Image effects
N/A

drush dst:ie
➜
➜ Generating Image Effects.
➜
➜ Image effect Scale created in Large (480×480)
➜ Image effect Scale created in Media Library thumbnail (220×220)
➜ Image effect Scale created in Medium (220×220)
➜ Image effect Scale and crop created in Thumbnail (100×100)
➜
➜ Finished generating Image Effects.

drush dst:ur
➜
➜ Generating user roles.
➜
➜ New role Site Configurator created.
➜ New role Content Editor created.
➜ New role Content Manager created.
➜
➜ Finished generating User roles.
➜

drush dst:w
➜
➜ Generating Workflows.
➜
➜ State Draft created successfully for workflow Editorial
➜ State In review created successfully for workflow Editorial
➜ State Published created successfully for workflow Editorial
➜ State Test created successfully for workflow Editorial
➜ State Archived created successfully for workflow Editorial
➜ Transitions Create New Draft created successfully for workflow Editorial
➜ Transitions Create New Draft created successfully for workflow Editorial
➜ Transitions Create New Draft created successfully for workflow Editorial
➜ Transitions Send to review created successfully for workflow Editorial
➜ Transitions Send to review created successfully for workflow Editorial
➜ Transitions Publish created successfully for workflow Editorial
➜ Transitions Publish created successfully for workflow Editorial
➜ Transitions Publish created successfully for workflow Editorial
➜ State ADraft created successfully for workflow Administrator
➜ State A In review created successfully for workflow Administrator
➜ State Published created successfully for workflow Administrator
➜ State Test created successfully for workflow Administrator
➜ State Archived created successfully for workflow Administrator
➜ To state Draft is not present for workflow Administrator
➜ Transitions Restore to Draft not created for workflow Administrator
➜ Transitions Archive created successfully for workflow Administrator
➜ Transitions Restore from archive created successfully for workflow Administrator
➜ New workflow Administrator created along with states and transitions.
➜
➜ Finished generating workflows, states and transitions.

Let's think about some other approach instead of adding direct dependency.

Originally posted by @vyasamit2007 in #84 (comment)

• Entity referece(Media type)
• Number (decimal)
• Number (float)
• Number (integer)
• List (integer)

Move redundant code of field storage used in Content type and Vocabulary generation commands to helper function in GeneralApi.

Create a drush command to create workflow, workflow states and workflow entities from DST sheet.

Currently we need add "google/apiclient" manually to the project, it should be a dependency of the module.
The module has composer.lock file and vendor folder, we should also remove it.

What is done?
Created this MR - #2

1. Created a module skeleton.
2. Added all the composer related stuff to make sure the contributors can get started with this.

Require discussion

• Should we go with the module OR should we just drush commands files?
• Shall we use the composer? If not required, we can remove it.

Require a new configuration to identify whether or not the row requires to be sync or not.

1. Column Name - Add a column to be used to identify whether the row needs to be synced or not.
2. Value - Add a value of the column to be used to identify whether the row needs to be synced or not.

@praveenkaransingh - Helper doesn't seem to be used anywhere. do we really need it?

Originally posted by @gauravgoyal in #94 (comment)

➜ Generating Menus.
➜
[error] Error: Call to a member function getData() on null in Drupal\dst_entity_generate\Commands\Menu->generateMenus() (line 66 of /var/www/eeavyas/docroot/modules/contrib/dst-entity-generate/src/Commands/Menu.php) #0 /var/www/eeavyas/docroot/modules/contrib/dst-entity-generate/src/Commands/GenerateAll.php(127): Drupal\dst_entity_generate\Commands\Menu->generateMenus()
#1 [internal function]: Drupal\dst_entity_generate\Commands\GenerateAll->generate(Array)
#2 /var/www/eeavyas/vendor/consolidation/annotated-command/src/CommandProcessor.php(257): call_user_func_array(Array, Array)
#3 /var/www/eeavyas/vendor/consolidation/annotated-command/src/CommandProcessor.php(212): Consolidation\AnnotatedCommand\CommandProcessor->runCommandCallback(Array, Object(Consolidation\AnnotatedCommand\CommandData))
#4 /var/www/eeavyas/vendor/consolidation/annotated-command/src/CommandProcessor.php(176): Consolidation\AnnotatedCommand\CommandProcessor->validateRunAndAlter(Array, Array, Object(Consolidation\AnnotatedCommand\CommandData))
#5 /var/www/eeavyas/vendor/consolidation/annotated-command/src/AnnotatedCommand.php(311): Consolidation\AnnotatedCommand\CommandProcessor->process(Object(Symfony\Component\Console\Output\ConsoleOutput), Array, Array, Object(Consolidation\AnnotatedCommand\CommandData))
#6 /var/www/eeavyas/vendor/symfony/console/Command/Command.php(255): Consolidation\AnnotatedCommand\AnnotatedCommand->execute(Object(Drush\Symfony\DrushArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#7 /var/www/eeavyas/vendor/symfony/console/Application.php(1027): Symfony\Component\Console\Command\Command->run(Object(Drush\Symfony\DrushArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#8 /var/www/eeavyas/vendor/symfony/console/Application.php(273): Symfony\Component\Console\Application->doRunCommand(Object(Consolidation\AnnotatedCommand\AnnotatedCommand), Object(Drush\Symfony\DrushArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#9 /var/www/eeavyas/vendor/symfony/console/Application.php(149): Symfony\Component\Console\Application->doRun(Object(Drush\Symfony\DrushArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#10 /var/www/eeavyas/vendor/drush/drush/src/Runtime/Runtime.php(118): Symfony\Component\Console\Application->run(Object(Drush\Symfony\DrushArgvInput), Object(Symfony\Component\Console\Output\ConsoleOutput))
#11 /var/www/eeavyas/vendor/drush/drush/src/Runtime/Runtime.php(49): Drush\Runtime\Runtime->doRun(Array, Object(Symfony\Component\Console\Output\ConsoleOutput))
#12 /var/www/eeavyas/vendor/drush/drush/drush.php(72): Drush\Runtime\Runtime->run(Array)
#13 /var/www/eeavyas/vendor/drush/drush/includes/preflight.inc(18): require('/var/www/eeavya...')
#14 phar:///usr/local/bin/drush/bin/drush.php(141): drush_main()
#15 /usr/local/bin/drush(10): require('phar:///usr/loc...')
#16 {main}.

On General settings form(/admin/config/dst_entity_generate/settings):

1. Display only those entities/Bundles who's entries present in respective tabs. E.g. In sheet, if there is no any data for Paragraph types, don't show to sync it.
2. In non-bundle entity selection, we are giving only All option to select. Provide all available entities/fields for selection.

Issue: Currently, if the field is mapped with multiple content types, only the first content type is generated with that field and others are not.

Ex: field_title | available in multiple content types, then only the first instance will have that field and other content types will not have the same field.

Expectation: We should consider the re-usage of any field.

• As we are using namespaces, we don't need to use dsteg as class name prefix.
• Service name should start with module name. like dst_entity_generate.general_api