{"id":28468444,"url":"https://github.com/bayatgames/conventions","last_synced_at":"2025-06-25T20:31:15.339Z","repository":{"id":286552361,"uuid":"947541006","full_name":"BayatGames/conventions","owner":"BayatGames","description":"Official development conventions, standards, and guidelines for Bayat projects. Includes coding standards, architecture principles, project workflows, and technical best practices to ensure consistency and quality across all teams.","archived":false,"fork":false,"pushed_at":"2025-04-07T05:28:33.000Z","size":1418,"stargazers_count":2,"open_issues_count":0,"forks_count":1,"subscribers_count":2,"default_branch":"main","last_synced_at":"2025-06-07T08:07:26.882Z","etag":null,"topics":["accessibility","architecture","best-practices","code-quality","coding-standards","consistency","conventional-changelog","conventional-commits","conventions","developer-experience","development-workflow","documentation","git-workflow","guidelines","naming-conventions","principles","productivity","refactoring","security-standards","standards"],"latest_commit_sha":null,"homepage":"https://bayat.io","language":"Shell","has_issues":true,"has_wiki":null,"has_pages":null,"mirror_url":null,"source_name":null,"license":null,"status":null,"scm":"git","pull_requests_enabled":true,"icon_url":"https://github.com/BayatGames.png","metadata":{"files":{"readme":"README.md","changelog":"CHANGELOG.md","contributing":"CONTRIBUTING.md","funding":null,"license":null,"code_of_conduct":null,"threat_model":null,"audit":null,"citation":null,"codeowners":null,"security":"docs/security/ai-governance.md","support":null,"governance":null,"roadmap":null,"authors":null,"dei":null,"publiccode":null,"codemeta":null}},"created_at":"2025-03-12T21:15:31.000Z","updated_at":"2025-05-29T08:40:33.000Z","dependencies_parsed_at":"2025-04-07T06:38:33.203Z","dependency_job_id":null,"html_url":"https://github.com/BayatGames/conventions","commit_stats":null,"previous_names":["bayatgames/conventions"],"tags_count":0,"template":false,"template_full_name":null,"purl":"pkg:github/BayatGames/conventions","repository_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BayatGames%2Fconventions","tags_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BayatGames%2Fconventions/tags","releases_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BayatGames%2Fconventions/releases","manifests_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BayatGames%2Fconventions/manifests","owner_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners/BayatGames","download_url":"https://codeload.github.com/BayatGames/conventions/tar.gz/refs/heads/main","sbom_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories/BayatGames%2Fconventions/sbom","host":{"name":"GitHub","url":"https://github.com","kind":"github","repositories_count":261948903,"owners_count":23234911,"icon_url":"https://github.com/github.png","version":null,"created_at":"2022-05-30T11:31:42.601Z","updated_at":"2022-07-04T15:15:14.044Z","host_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub","repositories_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repositories","repository_names_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/repository_names","owners_url":"https://repos.ecosyste.ms/api/v1/hosts/GitHub/owners"}},"keywords":["accessibility","architecture","best-practices","code-quality","coding-standards","consistency","conventional-changelog","conventional-commits","conventions","developer-experience","development-workflow","documentation","git-workflow","guidelines","naming-conventions","principles","productivity","refactoring","security-standards","standards"],"created_at":"2025-06-07T08:07:33.551Z","updated_at":"2025-06-25T20:31:15.333Z","avatar_url":"https://github.com/BayatGames.png","language":"Shell","funding_links":[],"categories":[],"sub_categories":[],"readme":"# Bayat Development Conventions\n\nThis repository contains the official development conventions, standards, and guidelines for all Bayat projects. Following these standards ensures consistency, quality, and efficiency across all teams and project types.\n\n## Overview\n\nThis repository defines the engineering standards, conventions, and best practices for all projects developed at Bayat. It serves as a single source of truth for development guidelines across various technologies and platforms.\n\n## Conventions and Standards\n\nOur conventions cover a wide range of topics, ensuring consistency and quality across our engineering efforts. Key areas include:\n\n* **Languages:** Standards for [JavaScript](docs/languages/javascript.md), [TypeScript](docs/languages/typescript.md), [Python](docs/languages/python.md), [C#](docs/languages/csharp.md), and others.\n* **Frameworks:** Best practices for frameworks like [React](docs/frameworks/react.md), [Node.js](docs/frameworks/nodejs.md), [Unity](docs/frameworks/unity.md), etc.\n* **Git Workflow:** Our branching strategy ([Bayat Git Flow](docs/git/flow.md)) and [Commit Message Standards](docs/git/commits.md).\n* **Architecture:** Guidelines for [API Design](docs/architecture/api-design.md), [Microservices](docs/architecture/microservices.md), and [ADRs](docs/architecture/architecture-decision-records.md).\n* **Quality:** Standards for [Testing](docs/quality/testing.md), [Code Reviews](docs/quality/code-reviews.md), and [CI/CD](docs/quality/ci-cd.md).\n* **Documentation:** Guidelines for [Technical](docs/documentation/technical.md), [Code](docs/documentation/code.md), and [API](docs/documentation/api.md) documentation.\n* **Security:** Best practices for [Secure Coding](docs/security/coding.md) and [Authentication](docs/security/authentication.md).\n\nFor a complete overview, please explore the `docs` directory.\n\n## Visual Overview\n\n```mermaid\ngraph TD\n    A[Conventions Root] --\u003e B(Languages);\n    A --\u003e C(Frameworks);\n    A --\u003e D(Architecture);\n    A --\u003e E(Quality);\n    A --\u003e F(Security);\n    A --\u003e G(Git);\n    A --\u003e H(Documentation);\n    A --\u003e I(Process);\n    D --\u003e J(API Design);\n    D --\u003e K(Microservices);\n    E --\u003e L(Testing);\n    E --\u003e M(CI/CD);\n    F --\u003e N(Secure Coding);\n    H --\u003e O(Code Docs);\n    H --\u003e P(API Docs);\n    subgraph Languages\n        B1[JS]\n        B2[TS]\n        B3[Python]\n    end\n    subgraph Frameworks\n        C1[React]\n        C2[Node]\n        C3[Unity]\n    end\n    B --\u003e B1 \u0026 B2 \u0026 B3;\n    C --\u003e C1 \u0026 C2 \u0026 C3;\n    J --\u003e P;\n    O --\u003e B1 \u0026 B2 \u0026 B3;\n    L --\u003e E;\n```\n\n## Purpose\n\nThe purpose of these conventions is to:\n\n1. **Ensure Consistency**: Maintain uniform practices across all projects\n2. **Improve Quality**: Follow industry best practices and proven patterns\n3. **Increase Efficiency**: Reduce decision fatigue and standardize workflows\n4. **Enable Collaboration**: Make it easier for team members to work on different projects\n5. **Simplify Onboarding**: Provide clear guidance for new team members\n\n## Getting Started\n\n* **New Developers**: Start with our [Developer Onboarding Path](docs/process/developer-onboarding-path.md)\n* **Contributing**: Read our [Contribution Guidelines](CONTRIBUTING.md)\n* **Recent Changes**: View our [Changelog](CHANGELOG.md)\n* **Self-Assessment**: Use our [Compliance Checklist](docs/quality/compliance-checklist.md)\n* **Example Implementations**: See [Example Repositories](examples/README.md)\n* **Cursor Integration**: Use our [Cursor IDE Templates](templates/README.md) for Unity, Tauri, React, Node.js, and full-stack projects\n\n## Structure\n\nThe conventions are organized into the following categories:\n\n### Git \u0026 Version Control\n\n* [Git Flow](docs/git/flow.md) - Branching strategy and workflow\n* [Commit Conventions](docs/git/commits.md) - Standards for commit messages\n* [Repository Structure](docs/git/repos.md) - Organization and configuration of repositories\n* [Multi-Repository Management](docs/cross-functional/multi-repository-standards.md) - Standards for managing multiple repositories\n\n### Languages\n\nLanguage-specific conventions for coding style, patterns, and best practices:\n\n* [C#](docs/languages/csharp.md) - Conventions for C# development\n* [JavaScript](docs/languages/javascript.md) - Standards for JavaScript development\n* [TypeScript](docs/languages/typescript.md) - TypeScript-specific guidelines\n* [Python](docs/languages/python.md) - Python coding standards\n* [C++](docs/languages/cpp.md) - C++ development guidelines\n* [C](docs/languages/c.md) - C development standards\n* [Java](docs/languages/java.md) - Java development standards\n* [Rust](docs/languages/rust.md) - Rust development standards\n* [Go](docs/languages/go.md) - Go development guidelines\n* [Swift](docs/languages/swift.md) - Swift development standards for Apple platforms\n* [Kotlin](docs/languages/kotlin.md) - Kotlin development standards\n* [PHP](docs/languages/php.md) - PHP development standards\n* [Ruby](docs/languages/ruby.md) - Ruby development standards\n* [Dart](docs/languages/dart.md) - Dart development standards\n* [Lua](docs/languages/lua.md) - Lua development standards\n* [Solidity](docs/languages/solidity.md) - Solidity blockchain development standards\n\n### Frameworks\n\nFramework-specific conventions and best practices:\n\n* [Unity](docs/frameworks/unity.md) - Guidelines for Unity game development\n* [Unreal Engine](docs/frameworks/unreal.md) - Standards for Unreal Engine development\n* [React](docs/frameworks/react.md) - React development patterns and practices\n* [Angular](docs/frameworks/angular.md) - Angular development standards\n* [Flutter](docs/frameworks/flutter.md) - Flutter and Dart best practices\n* [Node.js](docs/frameworks/nodejs.md) - Node.js development guidelines\n* [Electron.js](docs/frameworks/electron.md) - Electron.js desktop application standards\n* [Tauri](docs/frameworks/tauri.md) - Tauri desktop application guidelines\n* [Qt](docs/frameworks/qt.md) - Qt framework development standards\n* [.NET MAUI](docs/frameworks/maui.md) - .NET MAUI cross-platform application guidelines\n\n### Process \u0026 Workflows\n\nStandards for development processes and team workflows:\n\n* [Documentation Standards](docs/process/documentation-standards.md) - Guidelines for creating and maintaining documentation\n* [Onboarding Journey](docs/process/onboarding-journey.md) - Structured approach to developer onboarding\n* [Code Review Automation](docs/process/code-review-automation.md) - Standards for automating code review processes\n* [Developer Experience](docs/process/developer-experience.md) - Guidelines for improving developer experience\n* [Developer Experience Metrics](docs/process/developer-experience-metrics.md) - Standards for measuring developer experience\n* [Developer Experience Optimization](docs/process/developer-experience-optimization.md) - Standards for improving developer workflows and productivity\n* [Knowledge Management Protocol](docs/process/knowledge-management-protocol.md) - Standards for documentation maintenance and knowledge sharing\n* [Innovation Framework](docs/process/innovation-framework.md) - Guidelines for innovation processes and experimentation\n\n### Quality Assurance\n\nStandards for ensuring quality:\n\n* [Testing](docs/quality/testing.md) - Testing strategies and requirements\n* [Frontend Testing](docs/quality/frontend-testing.md) - Comprehensive frontend testing best practices\n* [Code Reviews](docs/quality/code-reviews.md) - Code review process and checklist\n* [CI/CD](docs/quality/ci-cd.md) - Continuous integration and deployment standards\n* [Code Generation](docs/quality/code-generation.md) - Standards for using AI-assisted code generation tools\n* [Code Refactoring](docs/quality/code-refactoring.md) - Guidelines for when and how to approach code refactoring\n\n### Documentation\n\nDocumentation standards:\n\n* [API Documentation](docs/documentation/api.md) - API documentation guidelines\n* [Code Documentation](docs/documentation/code.md) - Code-level documentation standards\n* [User Documentation](docs/documentation/user.md) - End-user documentation guidelines\n* [Technical Documentation](docs/documentation/technical.md) - System and architecture documentation\n* [End-User Documentation](docs/documentation/end-user-documentation.md) - Guidelines for creating user-facing documentation\n* [Technical Writing](docs/documentation/technical-writing.md) - Standards for technical writing\n* [Developer Portal](docs/documentation/developer-portal.md) - Standards for developer portal content and structure\n* [Interactive Documentation](docs/documentation/interactive-documentation.md) - Recommendations for implementing interactive documentation solutions\n\n### DevOps\n\nDevOps practices and standards:\n\n* [Deployment](docs/devops/deployment.md) - Deployment processes and environments\n* [Infrastructure as Code](docs/devops/infrastructure.md) - IaC standards and patterns\n* [Monitoring](docs/devops/monitoring.md) - Application and system monitoring standards\n* [Observability](docs/devops/observability.md) - Observability and telemetry guidelines\n* [Performance Monitoring](docs/devops/performance-monitoring-standards.md) - Standards for application performance monitoring\n* [Containerization](docs/devops/containers.md) - Docker and container best practices\n* [Disaster Recovery](docs/devops/disaster-recovery.md) - Disaster recovery and business continuity standards\n* [Incident Response](docs/devops/incident-response.md) - Incident response and postmortem processes\n\n### Security\n\nSecurity standards and best practices:\n\n* [Secure Coding](docs/security/coding.md) - Secure coding guidelines\n* [Authentication](docs/security/authentication.md) - Authentication best practices\n* [Password Policy](docs/security/password-policy.md) - Comprehensive password standards and implementation\n* [Data Protection](docs/security/data-protection.md) - Data security standards\n* [Vulnerability Management](docs/security/vulnerabilities.md) - Handling security vulnerabilities\n* [DevSecOps](docs/security/devsecops.md) - DevSecOps practices and integration\n* [Supply Chain Security](docs/security/supply-chain.md) - Software supply chain security standards\n* [AI Governance](docs/security/ai-governance.md) - Policies for responsible AI development and deployment\n* [Compliance Automation](docs/security/compliance-automation.md) - Standards for automating compliance checks\n* [Zero Trust Security](docs/security/zero-trust-security.md) - Zero trust security implementation\n* [Certificates and Compliance](docs/security/certificates-and-compliance.md) - Certificate management and compliance\n* [SAST/DAST](docs/security/sast-dast.md) - Static and Dynamic Application Security Testing\n\n### Project Architecture\n\nArchitecture standards:\n\n* [Microservices](docs/architecture/microservices.md) - Microservices architecture guidelines\n* [Monoliths](docs/architecture/monoliths.md) - Monolithic application architecture\n* [Frontend Architecture](docs/architecture/frontend.md) - Frontend architecture patterns\n* [Backend Architecture](docs/architecture/backend.md) - Backend architecture patterns\n* [Event-Driven Architecture](docs/architecture/event-driven.md) - Event-driven architecture patterns and best practices\n* [Feature Flags](docs/architecture/feature-flags.md) - Feature flag implementation standards and strategies\n* [Cloud-Native](docs/architecture/cloud-native.md) - Cloud-native application architecture\n* [Cloud Providers](docs/architecture/cloud-providers.md) - Cloud provider-specific guidelines and best practices\n* [API Design](docs/architecture/api-design.md) - API design standards and best practices\n* [API Versioning](docs/architecture/api-versioning.md) - API versioning and deprecation strategy\n* [Database Standards](docs/architecture/database-standards.md) - Database design and management standards\n* [Technical Debt](docs/architecture/technical-debt.md) - Technical debt management\n* [Technical Debt Quantification](docs/architecture/technical-debt-quantification.md) - Methods for measuring technical debt\n* [Technical Debt Management](docs/architecture/technical-debt-management.md) - Strategies for managing technical debt\n* [Performance Engineering](docs/architecture/performance-engineering.md) - Performance engineering standards\n* [Emerging Technologies](docs/architecture/emerging-technologies.md) - Guidelines for AI/ML, AR/VR, IoT, and edge computing\n* [Tech Radar](docs/architecture/tech-radar.md) - Technology recommendations and adoption guidance\n* [Serverless](docs/architecture/serverless.md) - Serverless architecture guidelines\n* [Blockchain and Web3](docs/architecture/blockchain-web3.md) - Blockchain and Web3 development standards\n* [AI and ML Integration](docs/architecture/ai-ml-integration.md) - AI and machine learning integration standards\n* [AI Engineering](docs/architecture/ai-engineering.md) - AI systems development, deployment, and maintenance standards\n* [AI/ML Engineering Standards](docs/architecture/ai-ml-engineering-standards.md) - Comprehensive AI/ML engineering standards\n* [MLOps](docs/architecture/mlops.md) - Machine learning operations standards and best practices\n* [Edge Computing](docs/architecture/edge-computing.md) - Edge computing architecture and implementation standards\n* [Data Engineering](docs/architecture/data-engineering.md) - Data engineering and analytics standards\n* [Data Engineering Governance](docs/architecture/data-engineering-governance.md) - Data governance and management\n* [Legacy Modernization](docs/architecture/legacy-modernization.md) - Legacy system modernization guidelines\n* [Quantum Computing](docs/architecture/quantum-computing.md) - Quantum computing readiness guidelines\n* [Low-Code/No-Code](docs/architecture/low-code-no-code.md) - Low-code/no-code integration guidelines\n* [Architecture Decision Records](docs/architecture/architecture-decision-records.md) - Standards for documenting architectural decisions\n* [Architecture Diagrams](docs/architecture/architecture-diagrams.md) - Standards and templates for creating architecture diagrams\n* [Platform Engineering](docs/architecture/platform-engineering.md) - Platform engineering standards\n* [GraphQL Standards](docs/architecture/graphql-standards.md) - Standards for GraphQL API development\n* [Event-Driven Architecture](docs/architecture/event-driven-architecture.md) - Detailed event-driven architecture standards\n* [Naming Conventions](docs/general/naming.md) - Standardized naming conventions for namespaces and package identifiers across all Bayat projects\n\n### Project-Specific Standards\n\nStandards for specific project types:\n\n* [Game Development](docs/projects/games.md) - Game-specific standards and patterns\n* [Web Applications](docs/projects/web.md) - Web application standards\n* [Mobile Applications](docs/projects/mobile.md) - Mobile application standards\n* [Mobile Development (Native)](docs/projects/mobile-native.md) - Native iOS and Android development best practices\n* [Desktop Applications](docs/projects/desktop.md) - Desktop application standards and patterns\n* [Native Multi-Platform](docs/projects/native-multiplatform.md) - Standards for native multi-platform development\n* [Cross-Platform Code Sharing](docs/projects/cross-platform-sharing.md) - Strategies for sharing code between web, mobile, and desktop platforms\n* [Libraries and Packages](docs/projects/libraries.md) - Standards for building libraries\n* [Progressive Web Apps](docs/projects/pwa-standards.md) - PWA development standards\n* [Design Systems](docs/projects/design-systems.md) - Design system development and maintenance\n* [Embedded Systems and IoT](docs/projects/embedded-iot.md) - Embedded systems and IoT development standards\n* [AR/VR/XR](docs/projects/ar-vr-xr.md) - Augmented, virtual, and mixed reality development standards\n\n### Development Environment\n\nStandards for development environment setup:\n\n* [Environment Setup](docs/environment/setup.md) - Development environment standards and configurations\n\n### Dependency Management\n\nGuidelines for managing dependencies:\n\n* [Dependency Management](docs/dependencies/management.md) - Best practices for managing external and internal dependencies\n* [Dependency Upgrade Strategies](docs/dependencies/upgrade-strategies.md) - Comprehensive standards for evaluating, upgrading, and maintaining dependencies\n\n### Release Management\n\nStandards for release processes:\n\n* [Release Management](docs/releases/management.md) - Guidelines for version management and release processes\n* [Release Templates](docs/releases/templates.md) - Templates for release documentation\n\n### Cross-functional Requirements\n\nStandards for cross-cutting concerns:\n\n* [Accessibility](docs/cross-functional/accessibility.md) - Accessibility compliance guidelines\n* [Accessibility Testing](docs/cross-functional/accessibility-testing.md) - Comprehensive accessibility testing standards and procedures\n* [Internationalization](docs/cross-functional/internationalization.md) - Internationalization and localization standards\n* [Performance](docs/cross-functional/performance.md) - Performance optimization guidelines\n* [Performance Budgets](docs/cross-functional/performance-budgets.md) - Specific metrics, targets, and measurement approaches for performance\n* [Frontend Optimization](docs/cross-functional/frontend-optimization.md) - Frontend performance optimization techniques and standards\n* [Green Software](docs/cross-functional/green-software.md) - Green software engineering standards\n* [Cultural and Regional](docs/cross-functional/cultural-regional.md) - Cultural and regional considerations in software development\n* [Ethical AI](docs/cross-functional/ethical-ai.md) - Ethical AI and responsible technology development\n* [Dark Mode Implementation](docs/cross-functional/dark-mode.md) - Guidelines for implementing dark mode across all platforms\n* [Inclusive Engineering](docs/cross-functional/inclusive-engineering.md) - Standards for creating inclusive software\n\n### Team Collaboration\n\nGuidelines for team collaboration:\n\n* [Team Collaboration](docs/collaboration/team-collaboration.md) - Standards for communication, meetings, and collaborative processes\n* [Remote Collaboration](docs/collaboration/remote-collaboration.md) - Standards and best practices for effective remote collaboration\n* [Community Contribution](docs/collaboration/community-contribution.md) - Guidelines for external contributions to open-source projects\n* [Mentorship and Knowledge Sharing](docs/collaboration/mentorship.md) - Structured approach to internal knowledge transfer and technical mentorship\n* [Community Standards](docs/collaboration/community-standards.md) - Standards for community engagement and governance\n\n### Learning Resources\n\nCurated learning resources:\n\n* [Learning Resources](docs/learning/resources.md) - Recommended books, courses, and resources for various technologies\n* [Knowledge Management](docs/learning/knowledge-management.md) - Knowledge management standards and practices\n\n### Project Templates and Starter Kits\n\nStandardized project templates:\n\n* [Project Templates](docs/templates/starter-kits.md) - Available project templates and starter kits\n\n### Tooling and Automation\n\nStandard tools and automation practices:\n\n* [Tooling and Automation](docs/tooling/automation.md) - Standard development tools and automation practices\n\n### Versioning Standards\n\nGuidelines for versioning:\n\n* [Versioning Standards](docs/versioning/standards.md) - Versioning schemes and practices\n\n### Legal Documentation\n\nLegal guidelines and standards:\n\n* [Licensing Guide](docs/legal/licensing-guide.md) - Guidelines for software licensing and compliance\n\n### Glossary\n\n* [Glossary of Terms](docs/glossary.md) - Definitions of common terms and acronyms used across projects\n\n## Using These Conventions\n\nAll team members are expected to follow these conventions for new projects and when contributing to existing ones. For legacy projects that don't follow these standards, a migration plan should be created when significant changes are planned.\n\n### Validation and Consistency\n\nTo ensure documentation consistency and completeness:\n\n1. Use the validation script to check if all documentation files are properly referenced:\n\n   ```bash\n   make validate\n   ```\n\n2. Check for broken links in documentation:\n\n   ```bash\n   make check-links\n   ```\n\n3. Run all validation checks at once:\n\n   ```bash\n   make check-all\n   ```\n\n### Document Templates\n\nWhen creating new documentation files:\n\n1. Use the document version header template from [Document Version Header](templates/document-version-header.md)\n2. Follow the section organization guide in [Section Organization](templates/section-organization.md)\n3. Keep documentation up to date, with correct version information\n\n## Contributing to Conventions\n\nThese conventions are not static and should evolve with industry trends and team experiences. To propose changes:\n\n1. Create a new branch from `main` following our [Git Flow](docs/git/flow.md)\n2. Make your proposed changes\n3. Submit a pull request with detailed explanation of the rationale for the change\n4. After review and approval, changes will be merged and communicated to all teams\n\n## Enforcement\n\nThese conventions are enforced through:\n\n1. Code review processes\n2. Automated linting and formatting tools\n3. CI/CD pipeline checks\n4. Regular training and workshops\n\nExceptions to these conventions may be allowed in specific circumstances but must be documented and approved by team leads.\n","project_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbayatgames%2Fconventions","html_url":"https://awesome.ecosyste.ms/projects/github.com%2Fbayatgames%2Fconventions","lists_url":"https://awesome.ecosyste.ms/api/v1/projects/github.com%2Fbayatgames%2Fconventions/lists"}