Add QuickFix links for missing configs and translations

[N1ebieski]

This PR improves my previous PR #415

1. Currently clicking on the link in the popover takes the user to the file. This PR adds support for a specific line where the new key should be inserted if the new key has a parent, for example:

2. PR adds support for .env values:

[TitasGailius]

hey @N1ebieski,

This is a great feature. Thanks for working on it!

For environment variables, we currently have a "quick fix" in place:

Would it be possible to add something similar for translations, instead of linking to them from the hover card?

[N1ebieski]

@TitasGailius This wasn't easy to achieve...

Needs more testing.

Contains #513

[N1ebieski]

Changes required according to: #513 (comment)

[N1ebieski]

@TitasGailius ok, summary:

1. I’ve removed the hover links and reverted the changes from Fix for QuickFix for vscode.Diagnostic.code #513
2. There are only "QuickFix" links:

• Add config to the file
• Add translation to the PHP file
• Add translation to the JSON file

3. Translation supports the locale parameter

[TitasGailius]

@N1ebieski this is much simpler now. Thanks.

One thought: since we already have all available config paths in getConfigs().items.configs, would it make sense to simply check for a match recursively?

For example, for nested.feature.item we could try, in order:

• nested.feature.item
• nested.feature
• nested

And if none match, we skip the code action.

[N1ebieski]

@TitasGailius We can do this for configs, but probably not for translations, because they only contain final keys. Did you check this?

[TitasGailius]

@N1ebieski you're right. We can do this for configs, but not for translations.

[N1ebieski]

@TitasGailius OK, let me know if I understand this correctly. Let’s assume we have a nested.php config file with the following contents:

return [
   'feature' => [
      'item' => 'value'
   ]
];

The user wants to access config('nested.new-feature.new-item'), so the extension recursively searches as follows:

1. nested.new-feature (not found),
2. nested (found).

As a result, it adds the following to the file:

return [
   'new-feature' => [
      'new-item' => ''
   ],
   'feature' => [
      'item' => 'value'
   ]
];

[TitasGailius]

@N1ebieski yep, I think that would cover all cases. Unless you have a better idea. 🙂

[N1ebieski]

@TitasGailius another summary:

1. I've changed the logic to support nested keys, according to Add QuickFix links for missing configs and translations #443 (comment)
2. For configs the code is simpler, because we have all the keys in the repository
3. For translations the code is more complicated, because we only have the final keys. I don't have a better idea how to simplify this further. I'm afraid that without changes of php-templates/translations.php this is impossible, but I would prefer to avoid modifying this file (so many other features depend on it)