Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

BUG - flp-config-sub-generator: FLP config is not writing unique i18n properties #2853

Open
1 of 8 tasks
korotkovao opened this issue Jan 31, 2025 · 0 comments
Open
1 of 8 tasks
Assignees

Comments

@korotkovao
Copy link
Contributor

Description

When adding flp config to a Fiori application, we are successfully validating that the semantic object and action are a unique combination, otherwise, we ask the user to confirm if they want to overwrite:

Image

However, adding different flp configurations to a Fiori application is using the i18n properties flpTitle and flpSubtitle multiple times in each manifest entry for the flp configuration and the associated i18n.properties file. This means that they would overwrite each other rather than be unique.

Steps to Reproduce

Steps to reproduce the behaviour:

  1. Create a Fiori project and add flp configuration
  2. Launch the app info page for the Fiori project and add a second flp configuration with a different title and subtitle.

Expected results

The manifest and i18n.properties entries should be unique, perhaps using the semantic object and action as a prefix, e.,g.:

i18n.properties:

Image

manifest.json:

Image

Actual results

Instead, the flpTitle and flpSubtitle are written multiple times to the manifest and i18n.properties file, thereby overwriting each other rather than being unique. See screenshot below:

Screenshots

i18n.properties entries:

Image

Associated manifest.json entries:

Image

Fiori tools component/version

Project Files

OS/Browser/Environment

OS:

  • Mac OS
  • Windows

Browser:

  • Chrome
  • Firefox
  • Edge

Environment:

  • Master
  • Staging
  • Production

Root Cause Analysis

Problem

{describe the problem}

Fix

{describe the fix}

Why was it missed

{Some explanation why this issue was missed during normal development/testing cycle}

How can we avoid this

{if we don’t want to see this type of issues anymore what we should do to prevent}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant