Remove g2_admin_settings

Also g2_admin_settings_submit and g2_admin_settings_validate : those three functions belong in Drupal\g2\Form\SettingsForm

First step: the main route, now with an auto-completion feature filtering out some unusable routes.

Converted the "main" settings.

Converted the formatting/tooltips and remote/client settings. More cleanup.

Rerolled on 8.x-1.0-alpha1.

Converted the API settings, also fixed the majority of the XML-RPC functions.

Converted the homonyms settings, removed duplicating "entries" config, unneeded remote.local config, more cleanup.

Completed conversion.

Merged to current dev HEAD.

Harshita mehna → made their first commit to this issue’s fork.

@Harshita mehna : this issue is fixed. Do not spend time on a fork. There are other live issues if you want to work on them :-)

@Harshita mehna
I see you have opened a merge request on an issue that is already closed. This creates unnecessary noise for the maintainers and anyone following an issue.

The amount of issues you have posted in the last few days leads other contributors to think you may be attempting to gamify the Drupal attribution system.

When you open a merge request or post a file it ticks the credit box for attribution and creates more work for maintainers when they close the issues. Please refrain from opening a merge request unless you are working on code.

I am going to go through some of the issues you are working on and give you individual examples on issue queue etiquette and how you can better improve your contributor experience working within the community.

Here is a list of resources to help you on your contribution journey, thanks!
Issue Queue Etiquette →
Contributor tasks →
Adding tags to issues and using tags →

~AmyJune, Core Mentor and CWG Community Health team member

Automatically closed - issue fixed for 2 weeks with no activity.