6192cca49d
* feat: add QR code functionality to invoice templates and enhance user experience * Introduced QR code generation for invoices, allowing users to include a QR code with customizable descriptions. * Updated invoice templates to display QR codes in both default and Stripe formats. * Enhanced form components to support QR code data input and visibility toggles. * Added utility functions for generating QR code data URLs. * Updated tests and snapshots to cover new QR code features and ensure visual consistency across templates. * Introduced a Code of Conduct document to promote a respectful community environment. * feat: enhance error handling and metadata management in invoice application * Updated error handling to reset invoice metadata to default upon error occurrence. * Refactored invoice client page to utilize a constant for default mobile tab value. * Improved metadata structure by including last visited mobile tab in the default metadata. * Adjusted schema to allow optional item name field for better flexibility in invoice items. * fix: downgrade react-pdf version and update mobile tab handling * Downgraded react-pdf from version 10.1.0 to 9.2.1 for compatibility. * Updated mobile tab handling to utilize the last visited tab from app metadata. * Refactored invoice client page to improve metadata management and ensure proper tab state persistence. * fix: remove redundant validation message for item name in invoice form * chore: update TODO list and comment out scroll to top effect in AppPageClient * Added a new issue link to the TODO.md for tracking. * Commented out the scroll to top effect in page.client.tsx for potential future use. * refactor: streamline viewport settings and restore scroll to top effect in AppPageClient * Simplified viewport configuration by removing unnecessary properties. * Restored the scroll to top effect in AppPageClient for improved user experience on initial render. * revert viewport * fix: prevent jumping on iOS when typing in textarea component * Added resize-none class to the textarea to improve user experience on iOS devices by preventing layout shifts while typing. * feat: reworked app logic, improved multi-page pdf layout, add/update e2e tests, improvements and bug fixes * Enhanced README.md with new features, including multi-page PDF support, QR code functionality, and live preview demos. * Added demo GIFs to showcase new features and improve user understanding. * Updated key features section for clarity and added a news & updates section for version tracking. * feat: add debounced error handling in invoice form component * Introduced a debounced callback for showing form errors to improve user experience by preventing rapid toast notifications. * Updated validation logic to utilize the new debounced error handling mechanism. * chore: update e2e snapshots and improved form errors toast * fix: improve PDF viewer and QR code layout in invoice templates * Added state management for page numbers in the mobile PDF viewer to handle multi-page documents. * Adjusted QR code positioning and size to prevent overlap with the fixed footer. * Updated padding in the Stripe template styles to resolve overlapping issues with the footer. * Updated TODO.md with additional context on preventing layout issues in PDF rendering. * feat: enhance invoice sharing logic with validation error handling * Added a new test to verify error toast visibility when the invoice form has validation errors. * Implemented state management for form validation errors in the AppPageClient. * Updated the InvoiceForm component to manage error states and trigger appropriate toasts for user feedback. * Ensured that the share button behavior reflects the form's validation state, improving user experience. * feat: enhance invoice template with authorized person fields * Added fields for Person Authorized to Receive and Person Authorized to Issue in the default invoice template. * Implemented visibility toggles for these fields in the invoice form. * Updated tests to verify the correct behavior of these fields in both default and Stripe invoice templates. * Enhanced PDF rendering to include names of authorized persons when applicable. * feat: implement cooldown for CTA toasts and update UI elements * Introduced a 5-minute cooldown for showing CTA toasts to enhance user experience. * Updated toast management logic in various components to respect the new cooldown. * Adjusted text color in the InvoiceClientPage for better visibility. * Refined tooltip content in the invoice form to clarify functionality. * Updated TODO.md to reflect changes in toast behavior. * feat: add unit column switch to stripe invoice template * Changed toggle labels from Show/hide to Show for various fields in the invoice forms and dialogs to enhance clarity. * Updated related test cases to reflect the new label changes across buyer, seller, and invoice templates. * Ensured consistency in user interface elements for better user experience. * chore: adjust text size * feat: update README and improve CTA toast logic * Replaced the EasyInvoicePDF logo with a new design and adjusted its size for better visibility. * Enhanced the call-to-action (CTA) toast functionality by refining the logic for showing toasts based on user interactions and session activity. * Updated text in the invoice form to clarify user actions and improve overall user experience. * Added a new logo image to the project assets. * update readme * refactor: improved mobile PDF viewer by importing the PDF worker directl, improve CTA toast logic, update readme * Renamed sections in README for clarity, including Live Preview to Invoice PDF Live Preview and Instant Download to Instant PDF Download. * Adjusted text in CTA toasts for better engagement. * Updated minimum time on page and interactions required for showing CTA toasts to enhance user experience. * Improved mobile PDF viewer by importing the PDF worker directly and addressing related issues in TODO.md. * fix: adjust CTA toast display timing for improved user experience * Updated the timeout for showing the CTA toast to 6 seconds after the invoice link notification, enhancing the visibility and timing of user prompts. * feat: Improved handling of invoice sharing logic to differentiate between mobile and desktop sharing methods, enhancing user experience. * Added a new command in package.json for running cloudflared tunnel. * Updated tests to verify the visibility of the share invoice link description toast. * Refined toast notifications in the AppPageClient to include new IDs for better tracking and user feedback. * Improved handling of invoice sharing logic to differentiate between mobile and desktop sharing methods, enhancing user experience. * feat: enhance toast notifications with unique IDs for better ux * fix: adjust invoice item limit in tests and update translations for total excluding tax * Reduced the maximum number of invoice items in the test from 20 to 15 to better align with URL limits. * Updated translations in the PDF i18n schema and related files to include total excluding tax in multiple languages. * Modified the invoice PDF template to display the total excluding tax using localized text. * fix qr code race condition * fix: update URL variable names and enhance sharing logic for better clarity * Renamed variables for generated URLs to improve code readability. * Updated sharing logic to ensure consistent use of the new variable names across mobile and desktop sharing methods. * Enhanced toast notifications to dismiss previous messages and track share events more effectively. * fix: update tax label helper message for clarity in invoice items * readme upd * fix: adjust idle time and minimum interactions for CTA toast display * Increased idle time from 3 seconds to 5 seconds to improve user engagement. * Updated minimum interactions required for showing the CTA toast from 2 to 3 to enhance user experience. * feat: implement cooldown logic for CTA toast display * Added functionality to track the last shown timestamp of the CTA toast using localStorage. * Introduced a 7-day cooldown period to prevent the toast from being shown multiple times within a week. * Updated context to reflect whether the CTA toast was shown recently, enhancing user experience. * chore: update dependencies and add GitHub workflows for linting and type checking * Updated package versions in package.json and pnpm-lock.yaml for better compatibility and performance. * Added GitHub Actions workflows for ESLint and TypeScript type checking to ensure code quality and consistency. * Enhanced buyer and seller management components with improved state management and type safety. * feat: enhance invoice sharing and download tracking * Added functionality to track the number of times invoices are shared via link and downloaded as PDF. * Updated the app metadata structure to include and . * Implemented logic to increment these counts upon sharing and downloading invoices, improving analytics and user engagement. * refactor: update README and TODO for clarity and consistency
5.1 KiB
Contributor Covenant Code of Conduct
Our Pledge
We as members, contributors, and leaders pledge to make participation in our community a harassment-free experience for everyone, regardless of age, body size, visible or invisible disability, ethnicity, sex characteristics, gender identity and expression, level of experience, education, socio-economic status, nationality, personal appearance, race, religion, or sexual identity and orientation.
We pledge to act and interact in ways that contribute to an open, welcoming, diverse, inclusive, and healthy community.
Our Standards
Examples of behavior that contributes to a positive environment for our community include:
- Demonstrating empathy and kindness toward other people
- Being respectful of differing opinions, viewpoints, and experiences
- Giving and gracefully accepting constructive feedback
- Accepting responsibility and apologizing to those affected by our mistakes, and learning from the experience
- Focusing on what is best not just for us as individuals, but for the overall community
Examples of unacceptable behavior include:
- The use of sexualized language or imagery, and sexual attention or advances of any kind
- Trolling, insulting or derogatory comments, and personal or political attacks
- Public or private harassment
- Publishing others' private information, such as a physical or email address, without their explicit permission
- Other conduct which could reasonably be considered inappropriate in a professional setting
Enforcement Responsibilities
Community leaders are responsible for clarifying and enforcing our standards of acceptable behavior and will take appropriate and fair corrective action in response to any behavior that they deem inappropriate, threatening, offensive, or harmful.
Community leaders have the right and responsibility to remove, edit, or reject comments, commits, code, wiki edits, issues, and other contributions that are not aligned to this Code of Conduct, and will communicate reasons for moderation decisions when appropriate.
Scope
This Code of Conduct applies within all community spaces, and also applies when an individual is officially representing the community in public spaces. Examples of representing our community include using an official e-mail address, posting via an official social media account, or acting as an appointed representative at an online or offline event.
Enforcement
Instances of abusive, harassing, or otherwise unacceptable behavior may be reported to the community leaders responsible for enforcement at vlad@mail.easyinvoicepdf.com. All complaints will be reviewed and investigated promptly and fairly.
All community leaders are obligated to respect the privacy and security of the reporter of any incident.
Enforcement Guidelines
Community leaders will follow these Community Impact 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 or unwelcome in the community.
Consequence: A private, written warning from community leaders, providing clarity around the nature of the violation and an explanation of why the behavior was inappropriate. A public apology may be requested.
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 the people involved, including unsolicited interaction with those enforcing the Code of Conduct, for a specified period of time. This includes avoiding interactions in community spaces as well as external channels like social media. Violating these terms may lead to a temporary or permanent ban.
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 community for a specified period of time. No public or private interaction with the people involved, including unsolicited interaction with those enforcing the Code of Conduct, is allowed during this period. Violating these terms may lead to a permanent ban.
4. Permanent Ban
Community Impact: Demonstrating a pattern of violation of community standards, including sustained inappropriate behavior, harassment of an individual, or aggression toward or disparagement of classes of individuals.
Consequence: A permanent ban from any sort of public interaction within the community.
Attribution
This Code of Conduct is adapted from the Contributor Covenant, version 2.0, available at https://www.contributor-covenant.org/version/2/0/code_of_conduct.html.
Community Impact Guidelines were inspired by Mozilla's code of conduct enforcement ladder.
For answers to common questions about this code of conduct, see the FAQ at https://www.contributor-covenant.org/faq. Translations are available at https://www.contributor-covenant.org/translations.