frankframework/frank-flow

Graphical flow editor for Frank configurations

Frank!Framework

Exchange, modify and aggregate messages between systems!

Open-Source, Low-Code & Stateless

The Frank!Framework is a framework that is completely configurable through XML configurations. Each Frank!Application may contain multiple configurations, and each configuration can consist of multiple end-to-end connections which we call 'adapters'. Configurations may be (re)loaded conditionally or individiually for optimal performance and customizability. The application may be managed and monitored through a web interface or REST API. See it in action: https://frank2example.frankframework.org

Running the Frank-Framework

The Frank!Framework can run on any java runtime, so you have your choice of application server. In our CI we test every PR and Release against Tomcat, Wildfly and JBoss, all these application servers may be used in production environments. You may create containers to run the framework using the beforementioned application servers. Please note that they are for development use only, more info about using and creating them can be found in Docker.md.

All production-ready containers will be pushed to our Nexus Repository Manager frankframework-docker repository. Helm charts are available in the charts repository.

Rebranding

The Ibis Adapter Framework has been renamed to "Frank!Framework". The migration is a work in progress, which is why you may encounter some old(er) names throughout our source code. Don't worry, everything will remain fully backwards compatible!

Releases

All our releases can be found on Maven central. Individual builds can be found on our Nexus repository here. For more information about our releases (such as improvements, non-backwards compatibility changes and security fixes), see the release notes of your version here.

Security

It is important to remember that the security of your Frank!Application is the result of the overall security of the hosting stack; the Java runtime, Application Server, Frank!Framework and your configuration.

It is our responsibility that there are no vulnerabilities in the Frank!Framework itself and all it's Java dependencies. In turn it is your responsibility to keep your Frank!Framework version up to date and ensure there are no vulnerabilities in your configuration. More information about reporting vulnerabilities, supported versions and how we deal with CVE's can be found in our Security Policy.

Feedback

For bug reports and feature requests, create a new issue at https://github.com/frankframework/frankframework/issues. For general questions feel free to post them on our discussions forum here on GitHub. If you would like to report a vulnerability, or have security concerns regarding the Frank!Framework, please email [email protected] and include the word "SECURITY" in the subject line.

Frank!Manual

In need of help? Our manual can be found at http://frank-manual.readthedocs.io. If you cannot find an answer to your question feel free to submit a question in discussions. If you want to contribute to our manual, the sources can be found here.

Contributing

Eager to help us expand or enhance our framework? Please read our Code of Conduct before Contributing.

frank-flow's Issues

Adding forwards and new pipes only for selected adapter

When adding forwards and new pipes or moving these objects they won't work in a configuration with multiple adapters.

Fix: every action must be done for only the selected adapter.

Show relevant icons next to the pipename for easy recognizability.

Is your feature request related to a problem? Please describe.
There are a lot of pipes. Searching for them can help, but there are still a lot of results when searching a term. Also, when looking at the flow, all the titles need to be read to know what they are.

Describe the solution you'd like
Giving groups of pipes some icons can help users to recognize the pipes more easily.

Add setting for nodes snapping to the grid

Is your feature request related to a problem? Please describe.
The nodes snap to grid, whether the user wants it or not.

Describe the solution you'd like
Add a setting that gives the user the choice.

• Add setting for snapping or no snapping
• Add setting for grid size (10, 25. 50, 100)

The size of canvas should be big enough to contain the selected configuration.

Is your feature request related to a problem? Please describe.
The canvas is too big for a small config and too small for a big config. You can also resize the canvas smaller than the config.

Describe the solution you'd like
Set the initial size to the width of the configuration after selecting a file.

Add setting for flow connection styles

Is your feature request related to a problem? Please describe.
The user doesn't have control over how the connections are shown.

Describe the solution you'd like

• Add the possibility to make the lines straight.
• Add the possibility to have the connections on the side of the nodes.

Make first click generate the flow

When clicking the flow, make sure it immediatly generates.

Make the differance between name and type of a node clear (on canvas and in option)

Is your feature request related to a problem? Please describe.
The names change order, and it isn't as clear as it could be.

Describe the solution you'd like
Keep the order the same.

Describe alternatives you've considered
Add small labels.

Additional context
Original request: Naam van de pipe en class van de pipe verwisselen in flow elementen (in de popup om attributen te bewerken staat naam ook boven en class eronder)

Make the flow look more proffesional

Fix minor css flaws.

Feature: Unclutter connectors

Is your feature request related to a problem? Please describe.
When there is some branching in a Frank configuration, the connectors easily become cluttered. See for example the picture at the bottom of this issue. This picture is already better then what you get when the elements are on a vertical line.

This issue may arise because all connections arrive at the same point on the top of the destination, while all connections leave from the same point on the bottom of the source element. The picture may improve when you use more connection points, for example to the left or to the right.

Describe the solution you'd like
We may extend tags with attributes about the graphical layout. We may introduce "originAnchor" and "targetAnchor". The allowed values for these might be "top", "right", "bottom" and "left".

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
See picture:

Create a GitHub action that runs the Cypress tests

Is your feature request related to a problem? Please describe.
When you push commits to a pull request of the frank-flow, then GitHub runs the GitHub actions that are configured in the repository. Reviewers of the pull request can see whether the GitHub actions failed or succeeded. They can use this information to decide whether to merge the pull request. We want to check that the Cypress tests succeed before a pull request is merged. Therefore we need a new GitHub action to run the Cypress tests.

Describe the solution you'd like
A clear and concise description of what you want to happen.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Adding a file with unsaved changes will discard the changes.

Describe the bug
When you alter an existing configuration and click on the add file button without saving, your changes will be discarded.

Reporter
Ruben

Category

• Editor

To Reproduce

1. open editor mode
2. make changes to existing config
3. add file
4. See changes discarded

Expected behavior
Expected changes to be saved.

Make the receiver draggable

Make receiver draggable and give the code possitions.

Add caching in the CI for the Frank!Runner

Is your feature request related to a problem? Please describe.
Running the cypress tests takes ~7 minutes on top of the 4 minutes built time because of the Frank!Runner.

Describe the solution you'd like
Cache the dependencies for the Frank!Runner so it starts faster.

Describe alternatives you've considered
Not using the Frank!Runner but the Framework JAR.

Additional context
Possible solution like at the IAF CI:

- name: Cache local Maven repository
      uses: actions/cache@v2
      env:
        cache-name: cache-maven-dependencies
      with:
        path: ~/.m2/repository
        key: ${{ runner.os }}-maven-${{ hashFiles('**/pom.xml') }}
        restore-keys: |
          ${{ runner.os }}-maven-

Source: https://github.com/ibissource/iaf/blob/master/.github/workflows/maven-build.yml

The flowchart and the text are not synchronized

Describe the bug
The flowchart is not synchronized with the text.

Reporter
Martijn Dirkse

Category
Use following Tags to categorize your bug report

• Flow chart

To Reproduce
Steps to reproduce the behavior:

1. Check out the frank-runner and the frank-flow from GitHub, such that they appear in a common parent directory.
2. Open that parent directory in Visual Studio Code.
3. Remove the Frank!Flow from you ~/.m2 directory.
4. Build the Frank!Flow using mvn install -P frontend (from the frank-flow checkout directory).
5. Start the Frank!Runner using the ANT task of Frank2Example4.
6. Open a browser (Chrome) pointing to localhost/frank-flow.
7. A drawing appears, although all the flow chart elements are placed on the same spot on the screen. This is not the point however of this issue.
8. Move the pipes and the exit to have a better view.
9. Press the button to the top-right to have both the text and the flow chart. The flow-chart looks like the following picture: See picture:

This is not synchronized with the text: The text contains the following:

<XmlSwitchPipe 
    name="ThirdPipe"
    xpathExpression="local-name(/*)"
>
    <Forward name="FirstPipe" path="SecondPipe"/>
    <Forward name="SecondPipe" path="EXIT"/>
</XmlSwitchPipe>

The text says that ThirdPipe points to SecondPipe and Exit. The link to SecondPipe is present but not the link to Exit.

Expected behavior
ThirdPipe should point to SecondPipe and Exit.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

When rerouting a connection from one node to another, it doesn't remove the old forward.

Describe the bug
When rerouting a connection from one node to another, it doesn't remove the old forward. It does add a new forward. So two forwards are present in the end.

Reporter
@philipsens and @jacodg

Category

• Flow

To Reproduce
Steps to reproduce the behavior:

1. Go to a configuration
2. Drag an existing connection from the arrow side to another node
3. See how the connection attaches to the node
4. See how the old connection still exists

Expected behavior
Old connection should be removed.

Screenshots

Additional information
Original request: Het lukt me niet om het eindpunt van een bestaande pijl om te leggen naar een andere pipe

When you move elements on the canvas, the XML in the text area is jeopardized

Describe the bug
When you move elements of a Frank configuration on the canvas, the x and y coordinates are updated in the text area. But while doing so, the Frank!Flow changes more than only the coordinates. The XML is invalidated in this change.

Reporter
Martijn Dirkse

Category
Use following Tags to categorize your bug report

• Flow chart
• Code editor

To Reproduce
Steps to reproduce the behavior:

1. Open the Frank!Flow such that an existing Frank configuration is selected. The configuration already assigns x and y coordinates to all elements. The values are quoted.
2. Move the elements around.
3. Read the text in the code editor. Observe that the text has become invalid XML.

Expected behavior
Only the coordinates are updated. No other changes occur.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
I started from the following XML:

<Configuration>
    	<Adapter name="TestFrankFlow">
		<Receiver name="TestFrankFlow">
			<JavaListener name="TestFrankFlow" x = "50" y = "0"/>
 		</Receiver>
		<Pipeline firstPipe="FirstPipe">
			<FixedResultPipe
				name="FirstPipe"
				returnString="&lt;FirstPipe/&gt;"
				x = "50" y = "150"
				>
				<Forward name="success" path="ThirdPipe"/>
			</FixedResultPipe>
			<FixedResultPipe
				name="SecondPipe"
				returnString="&lt;SecondPipe/&gt;"
				x = "50" y = "300"
				>
				<Forward name="success" path="ThirdPipe"/>
			</FixedResultPipe>
			<XmlSwitchPipe 
				name="ThirdPipe"
				xpathExpression="local-name(/*)"
				x = "250" y = "450"
				>
				<Forward name="FirstPipe" path="SecondPipe"/>
				<Forward name="SecondPipe" path="EXIT"/>
			</XmlSwitchPipe>
			<Exit path="EXIT" state="success"
				x = "250" y = "600"
			/>
		</Pipeline>
	</Adapter>
</Configuration>

I ended up with this XML:

<Configuration>
	<Adapter name="TestFrankFlow">
		<Receiver name="TestFrankFlow">
			<JavaListener name="TestFrankFlow" x = "50" y = "0"/>
		</Receiver>
		<Pipeline firstPipe="FirstPipe">
			<FixedResultPipe
				name="FirstPipe"
				returnString="&lt;FirstPipe/&gt;"
				x = "50" y = "150"
				>
				<Forward name="success" path="ThirdPipe"/>
			</FixedResultPipe>
			<FixedResultPipe
				name="SecondPipe"
				returnString="&lt;SecondPipe/&gt;"
				x x="318"""y="492""""""""
				>
				<Forward name="success" path="ThirdPipe"/>
			</FixedResultPipe>
			<XmlSwitchPipe 
				name="ThirdPipe"
				xpathExpression="local-name(/*)"
				x x="38" yyyy="314"
				>
				<Forward name="FirstPipe" path="SecondPipe"/>
				<Forward name="SecondPipe" path="EXIT"/>
			</XmlSwitchPipe>
			<Exit path="EXIT" state="success"
				x x="106" y y="579"
			/>
		</Pipeline>
	</Adapter>
</Configuration>

Canvas doesn't resize if the flow mode is opend.

Describe the bug
Canvas doesn't resize if the flow mode is opend.

Reporter
Me

Category

• Flow

To Reproduce
Steps to reproduce the behavior:

1. Go to editor mode;
2. Click on flow mode;
3. See default size canvas.

Expected behavior
The canvas should calculate minimum size and resize.

Screenshots
Correct size

After steps

Show selected pipe in Monaco editor

Is your feature request related to a problem? Please describe.
When looking at the editor it is difficult to find the selected pipe.

Describe the solution you'd like
Mark the selected pipe with a different color.

Additional context
Same feature can be found in the frank-flow 1.0 mvp

Undo/Redo not working correctly

Describe the bug
Undo and Redo are broken, I suspect the problem originates from the recent changes to the 'code-service' or 'monaco-editor component'.

Category
Use following Tags to categorize your bug report

• Flow chart
• Code editor

To Reproduce
Steps to reproduce the behavior:

1. Go to canvas
2. Drag pipe to new position
3. Click on 'Ctrl + Z'
4. See error

Expected behavior
For the code and flow to go back to previous state.

Maven errors while building the Frank!Flow for production

Describe the bug
When you build the Frank!Flow like mvn install -P frontend, there are ERROR messages in the output.

Reporter
Martijn Dirkse

Category
Use following Tags to categorize your bug report

• ??

To Reproduce
Steps to reproduce the behavior:

1. Checkout the Frank!Flow project from GitHub.

2. Open a MinGW command prompt.

3. Issue mvn install -P frontend from the checkout directory.

4. There are error messages:

    [INFO] Running 'npm install' in C:\Users\martijn\angular\frank-flow\src\frontend
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [WARNING] npm WARN @angular/[email protected] requires a peer of @angular/[email protected] but none is installed. You must install peer dependencies yourself.
    [ERROR]
    ...
    [INFO] > ng build --prod
    [INFO]
    [ERROR] - Generating browser application bundles...
    [ERROR] √ Browser application bundle generation complete.
    [ERROR] - Copying assets...
    [ERROR] √ Copying assets complete.
    [ERROR] - Generating index html...
    [ERROR] √ Index html generation complete.
    [INFO]
    [INFO] Initial Chunk Files
    ...
    [INFO] Build at: 2021-06-01T09:19:37.504Z - Hash: 4a9ea82908dca008799b - Time: 51532ms
    [ERROR]
    [ERROR] Warning: C:\Users\martijn\angular\frank-flow\src\frontend\src\app\flow\canvas\canvas.component.ts depends on 'dagre'. CommonJS or AMD dependencies can cause optimization bailouts.
    [ERROR] For more info see: https://angular.io/guide/build#configuring-commonjs-dependencies
    [ERROR]
    [ERROR] Warning: initial exceeded maximum budget. Budget 500.00 kB was not met by 840.33 kB with a total of 1.31 MB.
    [ERROR]
    [ERROR] Warning: ./src/assets/styles/_globals.scss (./node_modules/css-loader/dist/cjs.js??ref--13-1!./node_modules/postcss-loader/dist/cjs.js??ref--13-2!./node_modules/resolve-url-loader??ref--13-3!./node_modules/sass-loader/dist/cjs.js??ref--13-4!./src/assets/styles/_globals.scss)
    [ERROR] Module Warning (from ./node_modules/postcss-loader/dist/cjs.js):
    [ERROR] Warning
    [ERROR]
    [ERROR] (398:3) autoprefixer: end value has mixed support, consider using flex-end instead
    [ERROR]
    [ERROR]
    [INFO]
    [INFO] --- maven-resources-plugin:2.6:resources (default-resources) @ frank-flow ---
   

Expected behavior
The Maven build should not produce ERROR message. I would expect at most WARNING messages.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

Faster scroll speed in monaco editor

increase the scroll speed in the monaco editor.

The user should be able to perform CRUD actions for files and folders in the Explorer.

Is your feature request related to a problem? Please describe.
Managing a project via the file explorer can be cumbersome when switching a lot of files.

Describe the solution you'd like
Having an explorer like the one in IDE's can make this task a lot easier and quicker.
The crud actions are:

• Create files
• Read files
• Update files
• Delete files
• Create folders
• Read folders
• Update folder
• Delete folder

If a user makes changes via the file system, it should be possible to refresh the Explorer.

• Refresh Explorer
• Give message after adding or removing file
• Choose root as default folder

Code completion doesn't work anymore

Describe the bug
Code completion doesn't work anymore

Reporter
Jaco de Groot

Category

• Editor

To Reproduce
Steps to reproduce the behavior:

1. Open a configuration in the Frank!Flow
2. Use ctrl-tab
3. See that the code completion list only contains elements/attributes in the configuration and not from the Frank!Doc xsd

Expected behavior
Code completion showing info from Frank!Doc xsd

Screenshots
-

Additional context
-

Configuration inside configuration doesn't work

A configuration inside of a configuration will disrupt the regex.

Fix: display inner configuration as a seperate entity.

Lock pallete if XML is invalid. (Like canvas)

Is your feature request related to a problem? Please describe.
If the flow is locked, it is still possible to add items to the incorrect XML code.

Describe the solution you'd like
Lock the palette.

Related to #142

Feature: Keep cursor in monaco on the same position

The cursor position in the Monaco editor resets to the start every time the editor gets a new model value, or when a value is inserted.

The cursor should remain on the same position.

Pipe with multiple attributes will get faulty positions

Describe the bug
If a pipe has attributes that take multiple lines the positions will be broken.

Example:
<ApiListener name="listenerToConscience" uriPattern="adapter/hermes/address" method="GET"/>

Reporter
Ruben

Category

• Code editor

To Reproduce
Steps to reproduce the behavior:

1. Make a pipe which has attributes that take up multiple lines.
2. Drag the pipe in the flow
3. See that 'x' and 'y' attributes will be placed outside of the closing bracket.

Expected behavior
the 'x' and 'y' attributes should be put before the closing tag.

Screenshots

Feature: Lock the flow with an overlay stating an error if there is a parse error in the code.

Is your feature request related to a problem? Please describe.
Modifications to the flow won't get changed in the code, if the code is invalid.

Describe the solution you'd like
Lock the flow, stating that the invalid code should be corrected.

• Gather errors in worker and send them over
• Provide a graphical way to show the error
• Lock the flow

Describe alternatives you've considered
Remove the flow and show an error.

Selecting an empty file in the explorer, won't open it.

Describe the bug
Empty files can't be loaded into the editor when selected in the explorer.

Reporter
Me

Category
Use following Tags to categorize your bug report

• Explorer
• Editor

To Reproduce
Steps to reproduce the behavior:

1. Create an empty xml file in the file system.
2. Refresh the explorer.
3. Click on the created file.
4. Nothing happens.

Expected behavior
The file should be loaded into the editor (empty editor) at step 4.

Toggling graphical view and text view clears drawing area

Describe the bug
When you select the text view and then the flow-chart view, then the drawing area is cleared.

Reporter
Please state your name. If we don't know who is reporting, a solution of the issue might be delayed.

Category
Use following Tags to categorize your bug report

• Flow chart

To Reproduce
Steps to reproduce the behavior:

1. Check out the frank-runner and the frank-flow from GitHub, such that they appear in a common parent directory.
2. Open that parent directory in Visual Studio Code.
3. Remove the Frank!Flow from you ~/.m2 directory.
4. Build the Frank!Flow using mvn install -P frontend (from the frank-flow checkout directory).
5. Start the Frank!Runner using the ANT task of Frank2Example4.
6. Open a browser (Chrome) pointing to localhost/frank-flow.
7. A drawing appears, although all the flow chart elements are placed on the same spot on the screen. This is not the point however of this issue.
8. To the top-right, press the icon for text (</>).
9. To the top-right, press the icon for the flow chart (two buttons further to the right).
10. See the error. The drawing area is empty.

Expected behavior
In step 10, the drawing area should look like it looked after step 7.

Screenshots
Here are the buttons this issue is about.

Additional context
Add any other context about the problem here. (f.e. ladybug report / test adapter with larva test)

Empty canvas shouldn't show if the selected file, isn't a config

Is your feature request related to a problem? Please describe.
If a file is selected that isn't a config, the canvas renders empty and shows a parsing error.

Describe the solution you'd like
Detect if the file is a config or not and render the config based on that.

Describe alternatives you've considered
Change the error to "Select a config file"

Feature: Highlight the open file in the file tree

Is your feature request related to a problem? Please describe.
No

Describe the solution you'd like
Highlight the open file in the file tree so you know which file is open in the editor

Describe alternatives you've considered
-

Additional context

I have Configuration.xml open but you cannot see that in the file tree:

Place a new pipe in a better position when added with the Palette

Is your feature request related to a problem? Please describe.
When adding a pipe with the Palette it gets added to x100 y100.

Describe the solution you'd like
Place the pipe in the middle of the screen.

Describe alternatives you've considered
Let the graph algorithm determine the best place.

Additional context
Olriginal request: Bij toevoegen uit pallet de pipe op de plek laten komen die in beeld is (in het midden van het zichtbare gedeelte?) (had nu niet door dat het links boven pipes bij kwamen bij iedere klik, dacht dat er niks gebeurde en pipes toevoegen het niet deed)

If you select an innner directory you can't select the root directory anymore.

Describe the bug
After selecting an inner directory, selecting the root isn't possible anymore.

Reporter
Ruben

Category

• Explorer

To Reproduce

1. Go to explorer
2. Click on an inner directory
3. Click on the root directory
4. Add file
5. See that the inner direcory is still selected instead of the root.

Expected behavior
I expect the root to be the selected directory.

Add clean-code contraints to the ESLint

Is your feature request related to a problem? Please describe.
A lot of clean code principles rely on the code reviewers spotting the mistakes.

Describe the solution you'd like
Add these constraints to ESLint, so the developer will get a notice before committing.

Duplicate parsing errors should be grouped based on line and colum.

Is your feature request related to a problem? Please describe.
If you don't close a tag properly, saxes will throw a parse error for each character that "isn't supposed to be there".

Describe the solution you'd like
There should be one error message stating a start line and end line in which the error occurred.

Describe alternatives you've considered
@chiefruds: Alternatively for filtering the errors in the canvas you can also filter the errors here on the line and only add one unique error for each line.

Additional context
Discussion started: #173

When creating a new file with an already existing name, the original will get overwritten.

Describe the bug
The backend thinks the file needs to be updated.

Reporter
Me

Category

• Explorer

To Reproduce
Steps to reproduce the behavior:

1. Open code mode;
2. Create a file;
3. Edit this file;
4. Create a file with the same name;
5. See how your additions are removed.

Expected behavior
The frontend should give an error stating that the given name already exists.

Make it possible to configure sub elements for nodes (param, sender, listener).

Is your feature request related to a problem? Please describe.
The Frank!Flow can't perform all tasks.

Describe the solution you'd like
Implement adding subelements like "params", "senders" and "listeners". These should have their own attributes, like nodes.

The Maven build should include the frontend by default

Is your feature request related to a problem? Please describe.
Currently, doing mvn clean install in the root directory of the frank-flow produces a .jar that includes the backend but excludes the frontend. As a result, you get a HTTP 404 error when you access the frank-flow on localhost. This is quite confusing.

Describe the solution you'd like
The command mvn clean install should enable the frontend profile by default.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Bug: Monaco updates after an edit has been made in the XML code.

The code shouldn't update

Can we add a tooltip-text with the full

Is your feature request related to a problem? Please describe.
I was trying to save the file that was open in the code view of the Frank!Flow. I checked whether the file was saved by having it open in another editor. I saw that saving my file failed. I guessed that I was working on another file than I expected, but I could not easily verify that.

Describe the solution you'd like
Maybe a tooltip would be nice. The picture below shows the element for which I recommend a tooltip text with the full path:

Describe alternatives you've considered
We could show the full path somewhere else.

Additional context
Add any other context or screenshots about the feature request here.

You should see a clear error message when you have a backend jar without frontend

Is your feature request related to a problem? Please describe.
The Maven build of the frank-flow project produces a .jar that should be deployed on the server. There is a profile frontend. Only if this profile is enabled, then the frontend is added to this .jar file. We expect that developers will sometimes produce .jar files that do not include the frontend. On July 8 2021 Martijn, Jaco and Niels M. spent a lot of time debugging before they discovered that the .jar missed the frontend. A clear error message in this case will help.

Describe the solution you'd like
The URL /frank-flow should always produce some HTML page, also if the backend was built without the frontend profile. We can also add a Cypress test that calls the URL /frontend/api/configurations. If this URL produces a result, then we know that there is a frank-flow .jar on the classpath of the Java application on the server.

Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.

Additional context
Add any other context or screenshots about the feature request here.

Switching settings takes two tries

Describe the bug
When switching between dark mode and light mode it takes two tries to get the right result.

Reporter
Ruben

Category

• Settings

To Reproduce
Steps to reproduce the behavior:

1. Go to settings
2. Click on Dark mode
3. See incorrect switching behaviour

Expected behavior
I expect the theme to switch immediately.

Save attributes on pipes when the user closes the modal.

Is your feature request related to a problem? Please describe.
Currently, it uses a debounce, which is too quick sometimes.

Describe the solution you'd like
Save the changed attributes when the modal is closed.

Describe alternatives you've considered
Don't update the value in the options modal when inserting the new data.

Allow files and folders to be renamed

Is your feature request related to a problem? Please describe.
Renaming a file or folder can be useful if the name has to be changed.

Describe the solution you'd like
Add a 'modify' option, in which the filename or folder name can be changed.

• Backend endpoint
• Backend rename method
• Frontend calls
• Frontend modal

Describe alternatives you've considered
A 'modify project' button which lets you set the project name and configuration name.

Change forward values when a name or path is changed.

Is your feature request related to a problem? Please describe.
Changing a name or path will disconnect the pipes, because the value of the other forwards don't get changed.

Describe the solution you'd like
Change the value of the forwards.

Create recievers instead of listeners.

Describe the bug
Creating a new listener generates a new listener tag in the existing receiver.

Reporter
Me

Category
Use the following Tags to categorize your bug report

• Editor
• Palette

To Reproduce
Steps to reproduce the behavior:

1. Hybrid mode
2. Click on a listener in the pallete
3. Notice the generated xml

Expected behavior
Create new receiver.

Make a better readme

Improve the readme.

Clear the Editor after deleting the currently selected file.

Is your feature request related to a problem? Please describe.
If the current file gets deleted, the content stays in the Editor.

Describe the solution you'd like
Clear the Editor.

Update README documentation for Angular MVP release

Is your feature request related to a problem? Please describe.
The current README is outdated.

Describe the solution you'd like
Update the README to include the new launcher.

• Features
• Usage
• Development
• Flow settings (in config)