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 - extparameter does not work on fiori-tools-appreload #2544

Open
2 tasks
marianfoo opened this issue Nov 8, 2024 · 0 comments
Open
2 tasks

BUG - extparameter does not work on fiori-tools-appreload #2544

marianfoo opened this issue Nov 8, 2024 · 0 comments

Comments

@marianfoo
Copy link

Related Feature

Feature request: #1042

Description

When i run fiori-tools-appreload the property documented ext is not applied.

Steps to Reproduce

Steps to reproduce the behavior:

  1. use fiori-tools-appreload
  2. add ext to yaml
    - name: fiori-tools-appreload
      afterMiddleware: compression
      configuration:
        debug: true
        port: 35729
        path: webapp
        delay: 300
        ext: "xml,json,properties"
  1. start server
  2. see debug output, still default output (which also does not match doc)
Protocol version: 7
Exclusions: /\.git\//,/\.svn\//,/\.hg\//
Extensions: html,js,ts,json,xml,properties,change,variant,appdescr_variant,ctrl_variant,ctrl_variant_change,ctrl_variant_management_change
Polling: false

Documentation

<string> (default: html,js,json,xml,properties,change) Change this parameter to select a custom set of file extensions that are to be watched

Expected results

Only reload on js files

Actual results

Reloads on default extensions

Version/Components/Environment

@sap/ux-ui5-tooling: 1.15.3
Add any other context about the problem here
OS:

  • [ X] Mac OS
  • Windows
  • Other

Root Cause Analysis

Problem

{describe the problem}

Fix

{describe the fix}

Why was it missed

{Some explanation why this issue might have been 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