SilverLABS/littleshop
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
76efba55bd
littleshop/LittleShop/wwwroot/lib/hammerjs/CONTRIBUTING.md
sysadmin 76efba55bd feat: Phase 2.5 - Variant Collections Spreadsheet Editor 
Replaces JSON textarea with professional Excel-like spreadsheet interface for managing product variant properties.

Features:
- Handsontable 14.6.1 spreadsheet component
- Property presets (Size, Color, Material, Storage, Custom)
- Inline cell editing with Tab/Enter navigation
- Context menu for add/remove rows and columns
- Keyboard shortcuts (Ctrl+D delete, Ctrl+Enter save, Ctrl+Z undo)
- Mobile touch gestures (swipe to delete rows)
- Automatic JSON serialization on form submit
- Form validation before saving
- Comprehensive user guide documentation

Files Changed:
- LittleShop/package.json: NPM package management setup
- LittleShop/wwwroot/js/variant-editor.js: 400-line spreadsheet editor module
- LittleShop/wwwroot/lib/handsontable/: Handsontable library (Community Edition)
- LittleShop/wwwroot/lib/hammerjs/: Hammer.js touch gesture library
- LittleShop/Areas/Admin/Views/VariantCollections/Edit.cshtml: Spreadsheet UI integration
- VARIANT_COLLECTIONS_USER_GUIDE.md: Complete user guide (18+ pages)

Technical Details:
- Excel-like editing experience (no more manual JSON editing)
- Mobile-first responsive design
- Browser compatibility: Chrome 90+, Firefox 88+, Edge 90+, Safari 14+
- Touch-optimized for mobile administration
- Automatic data validation and error handling
2025-11-13 19:40:06 +00:00

1.6 KiB
Raw Blame History

Contributing to Hammer.js

Looking to contribute something to Hammer.js? Here's how you can help.

Reporting issues

We only accept issues that are bug reports or feature requests. Bugs must be isolated and reproducible problems that can be fixed within the Hammer.js. Please read the following guidelines before opening any issue.

  1. Read the documentation

  2. Search for existing issues. We get a lot of duplicate issues, and you'd help us out a lot by first checking if someone else has reported the same issue. Moreover, the issue may have already been resolved with a fix available. Also take a look if your problem is explained at the Wiki.

  3. Create an isolated and reproducible test case. Be sure the problem exists in Hammer's code with a reduced test case that should be included in each bug report.

  4. Include a live example. Make use of jsFiddle or jsBin to share your isolated test cases. Also, a screen capture would work, with tools like LICEcap.

  5. Share as much information as possible. Include operating system and version, browser and version, version of Hammer.js, customized or vanilla build, etc. where appropriate. Also include steps to reproduce the bug.

Pull requests

  1. Changes must be done in /src files, never just the compiled files. Also, don't commit the compiled files.

  2. Try not to pollute your pull request with unintended changes. Keep them simple and small

  3. Try to share which browsers your code has been tested in before submitting a pull request

  4. Write tests for your code, these can be found in /tests.