neo4j-labs · alfredorubin96 · Feb 18, 2025 · Jan 3, 2024 · Jan 3, 2024 · Jan 3, 2024
diff --git a/.github/workflows/master-deployment.yml b/.github/workflows/master-deployment.yml
@@ -79,7 +79,7 @@ jobs:
           context: .
           file: ./Dockerfile
           push: true
-          tags: ${{ secrets.DOCKER_HUB_LABS_USERNAME }}/neodash:latest,${{ secrets.DOCKER_HUB_LABS_USERNAME }}/neodash:2.4.9
+          tags: ${{ secrets.DOCKER_HUB_LABS_USERNAME }}/neodash:latest,${{ secrets.DOCKER_HUB_LABS_USERNAME }}/neodash:2.4.10
   build-docker-legacy:
     needs: build-test
     runs-on: neodash-runners
@@ -103,7 +103,7 @@ jobs:
           context: .
           file: ./Dockerfile
           push: true
-          tags: ${{ secrets.DOCKER_HUB_USERNAME }}/neodash:latest,${{ secrets.DOCKER_HUB_USERNAME }}/neodash:2.4.9
+          tags: ${{ secrets.DOCKER_HUB_USERNAME }}/neodash:latest,${{ secrets.DOCKER_HUB_USERNAME }}/neodash:2.4.10
   deploy-gallery:
     runs-on: neodash-runners
     strategy:

diff --git a/Dockerfile b/Dockerfile
@@ -44,4 +44,4 @@ USER nginx
 EXPOSE $NGINX_PORT
 
 HEALTHCHECK cmd curl --fail "http://localhost:$NGINX_PORT" || exit 1
-LABEL version="2.4.9"
+LABEL version="2.4.10"
diff --git a/changelog.md b/changelog.md
@@ -1,3 +1,19 @@
+## NeoDash 2.4.10 - Community contributions
+This is a minor release containing bug fixes and improvements contributed by the NeoDash community.
+- [#1039](/~https://github.com/neo4j-labs/neodash/pull/1039) - Fix default color scheme for bar charts
+- [#1038](/~https://github.com/neo4j-labs/neodash/pull/1038) - Fix rule-based styling for line charts
+- [#1036](/~https://github.com/neo4j-labs/neodash/pull/1036) - Fix table cell rule-based styling
+- [#1029](/~https://github.com/neo4j-labs/neodash/pull/1029) - Fix rule-based styling for numeric values
+- [#1028](/~https://github.com/neo4j-labs/neodash/pull/1028) - Fix OpenStreetMap leaflet display
+- [#1020](/~https://github.com/neo4j-labs/neodash/pull/1020) - Fix boolean handling in parameter selection
+- [#1014](/~https://github.com/neo4j-labs/neodash/pull/1014) - Remove autoPageSize flag (defaults to 0)
+- [#1009](/~https://github.com/neo4j-labs/neodash/pull/1009) - Fix SSO parameters lost on browser redirect
+- [#1008](/~https://github.com/neo4j-labs/neodash/pull/1008) - Fix existence check for `value.low`
+- [#1005](/~https://github.com/neo4j-labs/neodash/pull/1005) - Replace Neo4j Logo
+- [#1002](/~https://github.com/neo4j-labs/neodash/pull/1002) - Patch FAQ on supportability
+- [#999](/~https://github.com/neo4j-labs/neodash/pull/999) - Fix dark mode table header styling
+- [#956](/~https://github.com/neo4j-labs/neodash/pull/956) - Change default protocol to `neo4j+s`
+
 ## NeoDash 2.4.9
 This release adds some minor changes to documentation and implements some community contributions.
 - Added notice about project evolution: [#967](/~https://github.com/neo4j-labs/neodash/pull/967)

diff --git a/cypress/Page.js b/cypress/Page.js
@@ -31,6 +31,7 @@ export class Page {
 
   connectToNeo4j() {
     cy.get('#form-dialog-title', { timeout: 20000 }).should('contain', 'Connect to Neo4j');
+    cy.get('#protocol').type('neo4j{enter}');
     cy.get('#url').clear().type(DB_URL);
     cy.get('#dbusername').clear().type(DB_USERNAME);
     cy.get('#dbpassword').type(DB_PASSWORD);

diff --git a/cypress/e2e/start_page.cy.js b/cypress/e2e/start_page.cy.js
@@ -59,11 +59,11 @@ describe('NeoDash E2E Tests', () => {
       .should('contain', 'title')
       .and('contain', 'released')
       .and('not.contain', '__id');
-    // cy.get('main .react-grid-item:eq(2) .MuiDataGrid-virtualScroller .MuiDataGrid-row').should('have.length', 5);
-    // cy.get('main .react-grid-item:eq(2) .MuiDataGrid-footerContainer').should('contain', '1–5 of 8');
-    cy.get('main .react-grid-item:eq(2) .MuiDataGrid-footerContainer button[aria-label="Go to next page"]').click();
-    cy.get('main .react-grid-item:eq(2) .MuiDataGrid-virtualScroller .MuiDataGrid-row').should('have.length', 3);
-    cy.get('main .react-grid-item:eq(2) .MuiDataGrid-footerContainer').should('contain', '6–8 of 8');
+    // cy.get('main .react-grid-item:eq(2) .MuiDataGrid-virtualScroller .MuiDataGrid-row').should('have.length', 8);
+    // cy.get('main .react-grid-item:eq(2) .MuiDataGrid-footerContainer').should('contain', '1–8 of 8');
+    // cy.get('main .react-grid-item:eq(2) .MuiDataGrid-footerContainer button[aria-label="Go to next page"]').click();
+    // cy.get('main .react-grid-item:eq(2) .MuiDataGrid-virtualScroller .MuiDataGrid-row').should('have.length', 3);
+    // cy.get('main .react-grid-item:eq(2) .MuiDataGrid-footerContainer').should('contain', '6–8 of 8');
   });
 
   it('creates a bar chart report', () => {

diff --git a/docs/modules/ROOT/pages/developer-guide/adding-visualizations.adoc b/docs/modules/ROOT/pages/developer-guide/adding-visualizations.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Adding Visualizations
 
+include::../banner.adoc[]
+
 You can extend NeoDash with your own visualizations without diving deep
 into the core application. Likewise, adding a new customization to an
 existing report requires minimal changes.

diff --git a/docs/modules/ROOT/pages/developer-guide/build-and-run.adoc b/docs/modules/ROOT/pages/developer-guide/build-and-run.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Build & Run
 
+include::../banner.adoc[]
+
 To start developing the application, you will need to set up the
 development environment.
 

diff --git a/docs/modules/ROOT/pages/developer-guide/component-overview.adoc b/docs/modules/ROOT/pages/developer-guide/component-overview.adoc
@@ -2,6 +2,7 @@ include::../banner.adoc[]
 
 = Component Overview
 
+include::../banner.adoc[]
 
 The image below contains a high-level overview of the component
 hierarchy within the application. The following conceptual building

diff --git a/docs/modules/ROOT/pages/developer-guide/configuration.adoc b/docs/modules/ROOT/pages/developer-guide/configuration.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Configuration
 
+include::../banner.adoc[]
+
 When using a custom NeoDash deployment, there are several settings that
 can be configured. These mostly relate to
 link:../standalone-mode[Standalone Mode] and SSO configurations.
@@ -21,7 +23,7 @@ will look like this:
     "ssoProviders": [],
     "ssoDiscoveryUrl": "https://example.com",
     "standalone": false,
-    "standaloneProtocol": "neo4j",
+    "standaloneProtocol": "neo4j+s",
     "standaloneHost": "localhost",
     "standalonePort": "7687",
     "standaloneDatabase": "neo4j",
@@ -57,7 +59,7 @@ mode (false), or reader mode (true). The terms ``Reader mode'' and
 ``Standalone mode'' are used interchangibly.
 
 |standaloneProtocol |string |neo4j |When running in standalone mode, the
-protocol to used for the Neo4j driver. This shoudl be set to one of
+protocol to used for the Neo4j driver. This should be set to one of
 `neo4j`, `neo4j+s`, `neo4j+ssc`, `bolt`, `bolt+s`, or `bolt+ssc`.
 
 |standaloneHost |string |localhost |When running in standalone mode, the

diff --git a/docs/modules/ROOT/pages/developer-guide/contributing.adoc b/docs/modules/ROOT/pages/developer-guide/contributing.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Contributing
 
+include::../banner.adoc[]
+
 Contributions to the project are highly welcomed. Please consider
 creating a /~https://github.com/neo4j-labs/neodash/pulls[Pull Request].
 Ensure you start from the `develop` branch, and set the merge base to

diff --git a/docs/modules/ROOT/pages/developer-guide/deploy-a-build.adoc b/docs/modules/ROOT/pages/developer-guide/deploy-a-build.adoc
@@ -1,6 +1,7 @@
+= Deploy a Build
+
 include::../banner.adoc[]
 
-= Deploy a Build
 If you have a pre-built NeoDash application, you can easily deploy it on an any webserver.
 A NeoDash build is "just" a collection of HTML, CSS and JavaScript files, so it can run virtually anywhere.
 
@@ -39,7 +40,7 @@ Depending on the webserver type and version, this could be different directory.
 As an example - to copy the files to an nginx webserver using `scp`:
 
 ```bash
-scp neodash-2.4.9-labs username@host:/usr/share/nginx/html
+scp neodash-2.4.10-labs username@host:/usr/share/nginx/html
 ```
 
 NeoDash should now be visible by visiting your (sub)domain in the browser.

diff --git a/docs/modules/ROOT/pages/developer-guide/design.adoc b/docs/modules/ROOT/pages/developer-guide/design.adoc
@@ -2,6 +2,12 @@ include::../banner.adoc[]
 
 = Design
 
+include::../banner.adoc[]
+
+
+include::../banner.adoc[]
+
+
 This page contains some key guidelines for design of the application.
 This entails code architecture, as well as UX/UI design.
 

diff --git a/docs/modules/ROOT/pages/developer-guide/index.adoc b/docs/modules/ROOT/pages/developer-guide/index.adoc
@@ -2,6 +2,12 @@ include::../banner.adoc[]
 
 = Developer Guide
 
+include::../banner.adoc[]
+
+
+include::../banner.adoc[]
+
+
 This guide contains information for developers looking to deploy NeoDash, or extend it for their own needs. 
 
 - link:build-and-run[Build & Run] 

diff --git a/docs/modules/ROOT/pages/developer-guide/session-storage.adoc b/docs/modules/ROOT/pages/developer-guide/session-storage.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Session Storage
 
+include::../banner.adoc[]
+
 This reducer serves only to store data that we want to reset at each new session.
 To connect to it, just define a key and use the predefined actions to set a new pair (key,value) inside of it. 
 Inside the actions there is also an action to delete all the keys that match a precise prefix, it can be useful, for example, to wipe the sessionStorage state for a certain extension, if it stores the data inside the sessionStorage using a prefix (for example look at the query-translator extension at getSessionStorageHistoryKey).
diff --git a/docs/modules/ROOT/pages/developer-guide/standalone-mode.adoc b/docs/modules/ROOT/pages/developer-guide/standalone-mode.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Standalone Mode
 
+include::../banner.adoc[]
+
 Next to being a dashboard editor, NeoDash can be deployed in a
 `standalone mode' - allowing you set up a architecture to publish and
 read dashboards.
@@ -44,7 +46,7 @@ docker run  -it --rm -p 5005:5005 \
     -e ssoProviders=[] \
     -e ssoDiscoveryUrl="https://example.com" \
     -e standalone=true \
-    -e standaloneProtocol="neo4j" \
+    -e standaloneProtocol="neo4j+s" \
     -e standaloneHost="localhost" \
     -e standalonePort="7687" \
     -e standaloneDatabase="neo4j" \

diff --git a/docs/modules/ROOT/pages/developer-guide/state-management.adoc b/docs/modules/ROOT/pages/developer-guide/state-management.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = State Management
 
+include::../banner.adoc[]
+
 NeoDash is an application with a complex internal state. If you are
 planning to extend the application state in some way, make sure you are
 familiar with https://redux.js.org/[Redux] design patterns.
@@ -131,7 +133,7 @@ standalone mode.
     "ssoEnabled": false,
     "ssoProviders": [],
     "ssoDiscoveryUrl": "https://example.com",
-    "standaloneProtocol": "neo4j",
+    "standaloneProtocol": "neo4j+s",
     "standaloneHost": "localhost",
     "standalonePort": "7687",
     "standaloneDatabase": "neo4j",

diff --git a/docs/modules/ROOT/pages/developer-guide/style-configuration.adoc b/docs/modules/ROOT/pages/developer-guide/style-configuration.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Style Configuration
 
+include::../banner.adoc[]
+
 When using a custom NeoDash deployment, there are several theme variables that
 can be configured. These mostly relate to css tokens for
 link:https://cdn.jsdelivr.net/npm/@neo4j-ndl/base@1.4.0/lib/tokens/css/tokens.css[Needle] and some other brand specific options.

diff --git a/docs/modules/ROOT/pages/developer-guide/testing.adoc b/docs/modules/ROOT/pages/developer-guide/testing.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Testing 
 
+include::../banner.adoc[]
+
 NeoDash uses *Cypress* for automated testing. To install Cypress, check
 out the official
 https://docs.cypress.io/guides/getting-started/installing-cypress#What-you-ll-learn[installation

diff --git a/docs/modules/ROOT/pages/index.adoc b/docs/modules/ROOT/pages/index.adoc
@@ -1,6 +1,9 @@
 include::/banner.adoc[]
 
 = Introduction
+
+include::/banner.adoc[]
+
 This portal contains information on getting started with NeoDash - A Low-Code Dashboard Builder for Neo4j.
 
 NeoDash is an open source tool for visualizing your Neo4j data. It lets you group visualizations together as dashboards, and allow for interactions between reports.

diff --git a/docs/modules/ROOT/pages/quickstart.adoc b/docs/modules/ROOT/pages/quickstart.adoc
@@ -2,6 +2,8 @@ include::/banner.adoc[]
 
 = Quickstart
 
+include::/banner.adoc[]
+
 There are three easy ways to run NeoDash and start dashboarding your Neo4j data:
 
 . The latest version is always available online:

diff --git a/docs/modules/ROOT/pages/user-guide/access-control.adoc b/docs/modules/ROOT/pages/user-guide/access-control.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Access Control
 
+include::../banner.adoc[]
+
 The Access Control feature in NeoDash is a security measure that allows Users with write access or higher privileges to manage who has access to specific dashboards.
 
 

diff --git a/docs/modules/ROOT/pages/user-guide/bloom-integration.adoc b/docs/modules/ROOT/pages/user-guide/bloom-integration.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Bloom Integration
 
+include::../banner.adoc[]
+
 NeoDash can be linked to Neo4j Bloom perspectives by using
 https://neo4j.com/docs/bloom-user-guide/current/bloom-tutorial/deep-links/[Bloom
 Deep Links]. This functionality allows you to combine the power of graph

diff --git a/docs/modules/ROOT/pages/user-guide/dashboards.adoc b/docs/modules/ROOT/pages/user-guide/dashboards.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = Dashboards
 
+include::../banner.adoc[]
+
 In NeoDash, a dashboard consists of several pages, each of which can
 consist of multiple reports.
 

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/access-control-management.adoc b/docs/modules/ROOT/pages/user-guide/extensions/access-control-management.adoc
@@ -1,7 +1,8 @@
-include::../../banner.adoc[]
 
 = Access Control Management
 
+include::../../banner.adoc[]
+
 This extension lets you manage access control for roles and users, letting you assign users to roles as well as controlling which node labels can be read by a user.
 
 This extension is only visible to users with the role of "Administrator" or "Super User". Enabling this extension will allow the admin user to manage the labels of the roles in the database and then attach them to the users.

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/advanced-visualizations.adoc b/docs/modules/ROOT/pages/user-guide/extensions/advanced-visualizations.adoc
@@ -1,7 +1,8 @@
-include::../../banner.adoc[]
 
 = Advanced Visualizations
 
+include::../../banner.adoc[]
+
 Advanced visualizations let you extend your dashboard with complex, powerful visualizations beyond the standard visualizations.
 For specific use-cases, these visualizations may convey information that a simple visualization cannot.
 To use advanced visualizations, enable them in the **Extensions Window**. This makes them selectable inside reports, as well as add examples to the Example window.

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/forms.adoc b/docs/modules/ROOT/pages/user-guide/extensions/forms.adoc
@@ -1,7 +1,8 @@
-include::../../banner.adoc[]
 
 = Forms
 
+include::../../banner.adoc[]
+
 The 'forms' extension lets you combine different parameter selectors to update / modify your graph data.
 Update queries are predefined by the dashboard builder, and the user is limited to specifying the parameters for the query only.
 

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/index.adoc b/docs/modules/ROOT/pages/user-guide/extensions/index.adoc
@@ -1,7 +1,8 @@
-include::../../banner.adoc[]
 
 = Extensions
 
+include::../../banner.adoc[]
+
 Extensions provide a way to expand the basic functionality of NeoDash with extra features.
 To enable an extension, open up the extensions window by clicking the puzzle piece icon in the left-sidebar of the screen.
 This will open up the **Extensions Window**, which lets you toggle active extensions for the current dashboard.

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/natural-language-queries.adoc b/docs/modules/ROOT/pages/user-guide/extensions/natural-language-queries.adoc
@@ -1,6 +1,8 @@
-include::../../banner.adoc[]
 
 = Text2Cypher - Natural Language Queries
+
+include::../../banner.adoc[]
+
 Use natural language to generate Cypher queries in NeoDash. Connect to an LLM through an API, and let NeoDash use your database schema + the report types to generate queries automatically.
 
 == How it works

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/report-actions.adoc b/docs/modules/ROOT/pages/user-guide/extensions/report-actions.adoc
@@ -1,7 +1,8 @@
-include::../../banner.adoc[]
 
 = Report Actions 
 
+include::../../banner.adoc[]
+
 link:../#_2_pro_extensions[label:Pro&nbsp;Extension[]]
 
 Report actions let dashboard builders add interactivity into dashboards. Actions can be used to achieve:

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/rule-based-styling.adoc b/docs/modules/ROOT/pages/user-guide/extensions/rule-based-styling.adoc
@@ -1,7 +1,7 @@
-include::../../banner.adoc[]
 
 = Rule-Based Styling 
 
+include::../../banner.adoc[]
 
 The rule-based styling extension allows users to dynamically color elements in a visualization based on output values. This can be applied to tables, graphs, bar charts, line charts, and more. To use the extension, click on the 'rule-based styling' icon inside the settings of a report.
 

diff --git a/docs/modules/ROOT/pages/user-guide/extensions/workflows.adoc b/docs/modules/ROOT/pages/user-guide/extensions/workflows.adoc
@@ -1,7 +1,8 @@
-include::../../banner.adoc[]
 
 = Workflows
 
+include::../../banner.adoc[]
+
 Introducing an advanced extension for creating, managing, and running workflows with Cypher queries. Simplify ETL flows, execute complex query chains, and run graph data science workloads effortlessly from Neodash.
 
 == Enable the extension

diff --git a/docs/modules/ROOT/pages/user-guide/faq.adoc b/docs/modules/ROOT/pages/user-guide/faq.adoc
@@ -2,6 +2,8 @@ include::../banner.adoc[]
 
 = FAQ
 
+include::../banner.adoc[]
+
 == 1. How can I learn more about NeoDash?
 
 To learn more, check out the following list of resources (blogs, videos
@@ -48,17 +50,8 @@ If you need help setting this up, please contact the NeoDash team.
 
 == 4. Is NeoDash Production Ready?
 
-NeoDash is safe to be used in a production environment. As it is a
-reporting tool, keep the following things in mind: 
-
-- Always use *read-only* Neo4j accounts when connecting to a dashboard. 
-- Always deploy NeoDash with SSL, so that an encrypted Neo4j connection must be
-used. 
-- As NeoDash accesses Neo4j directly, make sure you only give
-access to the right people. As a rule of thumb, you should give NeoDash
-access to the people that can also see Bloom.
-
-For other questions regarding setting up your own production deployment, contact the NeoDash team.
+NeoDash Labs is an experimental tool without official support.
+For production-grade usage with Neo4j Enterprise Edition, we recommend a `NeoDash commercial` license.
 
 == 5. Can I use NeoDash with Neo4j Community Edition?
Original file line number	Diff line number	Diff line change
Expand Up		@@ -2,6 +2,8 @@ include::../banner.adoc[]

		= Access Control

		include::../banner.adoc[]

		The Access Control feature in NeoDash is a security measure that allows Users with write access or higher privileges to manage who has access to specific dashboards.


Expand Down