[examples] Remove node expand/fold example and related code #492

[Sohaibkundi2]

The node expand/fold example was broken locally with 'Uncaught ReferenceError: module is not defined' and is no longer used in OpenWISP.

Removed:

• example_templates/netjsongraph-nodeExpand.html
• public/assets/data/netjsongraph-foldNodes.json
• related import and entry in test/browser.test.utils.js
• card link from index.html

Description of Changes

Removes the broken node expand/fold example as discussed in #492.
The example was failing locally with Uncaught ReferenceError: module is not defined.
This is a focused PR addressing only the nodeExpand removal item from the issue.

Checklist

• I have read the OpenWISP Contributing Guidelines.
• I have manually tested the changes proposed in this pull request.
• I have written new test cases for new code and/or updated existing tests for changes to existing code.
• I have updated the documentation.

Reference to Existing Issue

Related to #492

Screenshot

Not applicable - this PR removes a broken example, no visual changes.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 8e01f50f-2fe1-40b6-8462-39b397963a24

📥 Commits

Reviewing files that changed from the base of the PR and between 4fe9913 and 52273ee.

📒 Files selected for processing (1)

• index.html

💤 Files with no reviewable changes (1)

• index.html

---

📝 Walkthrough

Walkthrough

This pull request removes the "Nodes expand or fold" example and its assets: the example template public/example_templates/netjsongraph-nodeExpand.html, the backing data public/assets/data/netjsongraph-foldNodes.json, the example card link in index.html, and the corresponding mapping entry in test/browser.test.utils.js. No other application logic, exported APIs, or runtime code paths were modified.

Sequence Diagram(s)

(Skipped — change is removal of example files and does not introduce or alter multi-component control flow requiring a sequence diagram.)

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• [chores] Improve examples (reordered, minor test improvements) #493 — Edits/removes the same netjsongraph-nodeExpand example and related files; directly related to this removal.
• [change] Reduce library size #392 #425 — Also removes the netjsongraph-nodeExpand demo and associated test/data files; strongly related.

Suggested reviewers

• nemesifier

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Title check	⚠️ Warning	The title uses '[examples]' instead of a required type prefix (fix, change, feature, qa, ci, chores, docs) and does not follow the specified format.	Update title to follow '[type] Descriptive title' format, e.g., '[chores] Remove node expand/fold example and related code #492' or '[fix] Remove broken node expand/fold example #492'.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Description check	✅ Passed	The description includes most required sections and checklist items are mostly completed, though the PR notes that new/updated tests were not written for code removal.
Bug Fixes	✅ Passed	PR removes broken example files outside npm distribution (dist/, src/). Not applicable to bug fix check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[nemesifier]

This example needed some logic in the library which would remain lingering with no benefit. We must remove the logic on which the examples relied too.

[openwisp-companion]

Hi @Sohaibkundi2 👋,

This pull request has been marked as stale due to 22 days of inactivity after changes were requested.

As a result, any linked issues are being unassigned from you so other contributors can pick them up.

However, you can still continue working on this PR! If you push new commits or respond to the review feedback:

• The issue will be reassigned to you
• Your contribution is still very welcome

If you need more time or have questions about the requested changes, please let us know. We're happy to help! 🤝