Dev

.github/workflows/main.yml

@@ -20,7 +20,7 @@ jobs:
             - uses: actions/checkout@v4
             - uses: pnpm/action-setup@v4
               with:
-                  version: 9.15.1
+                  version: 9.15.2
             - uses: actions/setup-node@v4
               with:
                   node-version: ${{ matrix.node_version }}

CODE_OF_CONDUCT.md

@@ -0,0 +1,76 @@
+# Code of Conduct
+
+## Our Pledge
+In the interest of fostering an open and welcoming environment, we as contributors and maintainers pledge to make participation in our project and community a harassment-free experience for everyone, regardless of:
+- Age
+- Body size
+- Disability
+- Ethnicity
+- Gender identity and expression
+- Level of experience
+- Nationality
+- Personal appearance
+- Race
+- Religion
+- Sexual identity and orientation
+- Socioeconomic status
+
+We are committed to maintaining a respectful, friendly, and productive community.
+
+## Our Standards
+Examples of behavior that contributes to creating a positive environment include:
+- Demonstrating empathy and kindness toward other people
+- Being respectful of differing opinions, viewpoints, and experiences
+- Giving and gracefully accepting constructive feedback
+- Focusing on what is best for the community
+- Showing patience and humility when dealing with mistakes or oversights
+
+Examples of unacceptable behavior include:
+- The use of sexualized language or imagery
+- Insults, derogatory or demeaning comments, and personal or political attacks
+- Public or private harassment
+- Publishing others’ private information, such as physical or electronic addresses, without explicit permission
+- Other conduct which could reasonably be considered inappropriate in a professional setting
+
+## Our Responsibilities
+Project maintainers are responsible for clarifying the standards of acceptable behavior and are expected to take appropriate and fair corrective action in response to any instances of unacceptable behavior.
+
+Project maintainers have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that do not align with this Code of Conduct. They may also temporarily or permanently ban any contributor for behaviors they deem inappropriate, threatening, offensive, or harmful.
+
+## Scope
+This Code of Conduct applies both within project spaces and in public spaces when an individual is representing the project or its community. Examples of representing a project or community include:
+- Posting via an official social media account
+- Acting as a project representative at online or offline events
+
+## Enforcement
+Instances of abusive, harassing, or otherwise unacceptable behavior may be reported by contacting the project team at **[INSERT CONTACT EMAIL OR OTHER METHOD]**. All complaints will be reviewed and investigated promptly and fairly.
+
+Project maintainers have the right and responsibility to take appropriate action, which may include but is not limited to:
+- Giving warnings
+- Removing contributions
+- Banning offenders from the project
+
+## Enforcement Guidelines
+Project maintainers will follow these guidelines in determining the consequences for any action they deem in violation of this Code of Conduct:
+1. **Correction**
+   Community impact: Use of inappropriate language or other behavior deemed unprofessional.
+   Consequence: A private, written warning and an explanation of why the behavior was inappropriate.
+
+2. **Warning**
+   Community impact: A violation through a single incident or series of actions.
+   Consequence: A warning with consequences for continued behavior. No interaction with those involved (including unsolicited interaction with those enforcing the Code of Conduct) for a specified period of time. The project team will step in to mediate or interrupt further conflicts.
+
+3. **Temporary Ban**
+   Community impact: A serious violation of community standards, including sustained inappropriate behavior.
+   Consequence: A temporary ban from any sort of interaction or public communication with the project for a specified period of time.
+
+4. **Permanent Ban**
+   Community impact: Demonstrating a pattern of violation of community standards or severe, sustained harassment of an individual.
+   Consequence: A permanent ban from all community interaction.
+
+## Attribution
+This Code of Conduct is adapted from the [Contributor Covenant][homepage], version 2.1, available at [https://www.contributor-covenant.org/version/2/1/code_of_conduct.html](https://www.contributor-covenant.org/version/2/1/code_of_conduct.html).
+
+For answers to common questions about this Code of Conduct, see the FAQ at [https://www.contributor-covenant.org/faq](https://www.contributor-covenant.org/faq).
+
+[homepage]: https://www.contributor-covenant.org

CONTRIBUTING.md

@@ -0,0 +1,64 @@
+# Contributing Guidelines
+
+Thank you for considering contributing to this project! We appreciate any support or help that makes this project better.
+
+## Table of Contents
+1. [How Can I Contribute?](#how-can-i-contribute)
+    - [Reporting Bugs](#reporting-bugs)
+    - [Suggesting Features or Enhancements](#suggesting-features-or-enhancements)
+    - [Submitting Pull Requests](#submitting-pull-requests)
+2. [Style & Conventions](#style--conventions)
+3. [Contact](#contact)
+
+---
+
+## How Can I Contribute?
+
+### Reporting Bugs
+1. **Check the issue tracker**
+   Before reporting a bug, check if it’s already been reported.
+2. **Open a new issue**
+   If no existing issue matches your findings, open a new issue.
+    - Provide a clear description of the bug.
+    - Include steps to reproduce the bug, along with any relevant logs or screenshots.
+    - Specify the environment (e.g., operating system, browser version) if relevant.
+
+### Suggesting Features or Enhancements
+1. **Search existing issues**
+   Similar to reporting bugs, search the issue tracker to see if your feature or enhancement has already been discussed.
+2. **Open a feature request**
+   If it’s a new idea, open an issue titled “Feature Request: [Your idea]” and describe:
+    - What problem does this feature solve?
+    - What are its potential use cases?
+    - Any suggested implementation details?
+
+### Submitting Pull Requests
+1. **Fork the repository**
+   Create your own copy to work on.
+2. **Create a new branch**
+   It’s best practice to name your branch something descriptive, like `feature/new-thing` or `fix/bug-description`.
+3. **Make your changes**
+    - Keep commits focused on a single goal.
+    - Write clear, descriptive commit messages.
+4. **Test your changes**
+    - Ensure all tests pass locally.
+    - Consider adding new tests if you introduce new features or fix bugs.
+5. **Open a pull request**
+    - Reference any related open issues in your pull request description.
+    - Provide a summary of the changes you made and why they’re important.
+6. **Review & discussion**
+    - Be prepared to discuss your changes and make revisions if needed.
+    - The maintainers may request changes or suggest improvements.
+7. **Merging**
+    - Once approved, your PR will be merged by a maintainer.
+
+## Style & Conventions
+- **Documentation**: Keep inline documentation clear and concise.
+- **Code Structure**: Follow any existing code patterns or architectural decisions in the project.
+- **Naming Conventions**: Use descriptive variable, function, and class names.
+- **Linting / Formatting**: Run the linting and formatting tools before opening a pull request.
+
+## Contact
+If you have any questions or concerns about contributing, feel free to reach out by opening an issue or emailing us at [[email protected]](mailto:[email protected]).
+
+Thank you again for your interest in contributing to this project!

README.md

@@ -56,6 +56,13 @@ Demo credentials:
   - Multi-language interface
   - Inventory management across properties
 
+## Floor Plan Editor
+
+Here’s what the Floor Plan Editor looks like:
+
+![Floor Editor Screenshot](screenshots/floor-editor.png)
+
+
 ## Project Structure
 
 - frontend: Main web application

package.json

@@ -48,10 +48,11 @@
     "engines": {
         "node": ">= 22.9.0"
     },
-    "packageManager": "[email protected].1",
+    "packageManager": "[email protected].2",
     "pnpm": {
         "overrides": {
-            "jsdom": "25.0.1"
+            "jsdom": "25.0.1",
+            "uri-js": "npm:uri-js-replace"
         }
     }
 }

packages/floor-creator/package.json

@@ -26,7 +26,6 @@
         "@types/hammerjs": "2.0.46",
         "@types/node": "22.10.2",
         "@vitest/browser": "catalog:",
-        "cheerio": "1.0.0",
         "vitest": "catalog:"
     },
     "keywords": [