ConfigurableLanguageManagerInterface::getLanguageConfigOverride() and LanguageConfigFactoryOverrideInterface::getOverride() should document that they return a new config object if none exists

Modified both function's docs to specify that if there is no config override for the specified language code, a new one is instantiated.

Thanks for working on this!

Left a comment on the MR. Since the comment is related to the langCode, description should go under that variable.

Is anything else needed for this issue?
I'd be happy to work on it if necessary!

Good practice issue summary should be complete

peter majmesku → made their first commit to this issue’s fork.

Looks fine. I fixed spelling. Improved the explanation and line breaks. Can this small change could be merged, please?

There was already a working MR can we use that one please

Also it was in NW for an issue summary update which is still needed

Thanks

I could not push into the existing MR. Even with requested push access. What do you mean with issue summary?

I think what I originally wrote for this issue is unclear.

What I was trying to say was that one of the following happen:

1. There is config data already: a LanguageConfigOverride object is created, which holds this data
2. There is no config data: a LanguageConfigOverride is created anyway, which is empty.

So it's not so much that 'if there's no data, an object is created', rather 'an object is always created; if there's no data it will be empty'

  public function getOverride($langcode, $name) {
    $storage = $this->getStorage($langcode);
    $data = $storage->read($name);

    $override = new LanguageConfigOverride(
      $name,
      $storage,
      $this->typedConfigManager,
      $this->eventDispatcher
    );

    if (!empty($data)) {
      $override->initWithData($data);
    }
    return $override;
  }

Hi Everyone

I’ve improved the comment as joachim suggested.
Could someone please review this MR and let me know if anything else needs to be done?
I made changes in both MRs, but I’m not sure which one is the correct one to merge when it's ready.

Issue summary needs to be updated