Conversation
|
Important Review skippedAuto reviews are disabled on base/target branches other than the default branch. Please check the settings in the CodeRabbit UI or the You can disable this status message by setting the WalkthroughThis pull request updates numerous Arabic translation files across multiple Sylius bundles. The changes rephrase and refine text in UI labels, emails, notifications, error messages, and validation prompts. Several new translation keys have been introduced while some deprecated entries were removed. Adjustments span messages, flashes, and validators for modules such as Admin, Attribute, Channel, Core, Currency, Customer, Locale, Order, Payment, Payum, Product, Promotion, Review, Shipping, Shop, Taxation, Taxonomy, Ui, and User. No modifications were made to exported or public entities. Changes
Poem
🪧 TipsChatThere are 3 ways to chat with CodeRabbit:
Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments. CodeRabbit Commands (Invoked using PR comments)
Other keywords and placeholders
CodeRabbit Configuration File (
|
✅ Preview Environment deployed on Bunnyshell
See: Environment Details | Pipeline Logs Available commands:
|
There was a problem hiding this comment.
Actionable comments posted: 2
🔭 Outside diff range comments (1)
src/Sylius/Bundle/PaymentBundle/Resources/translations/validators.ar.yml (1)
49-53:⚠️ Potential issueDuplicate Payment Method Key – Code Validations
A new "payment_method" block for code validations has been introduced. Caution: In YAML, duplicate keys at the same level may override earlier entries. Please verify that these entries are merged as intended or consider combining them under a single "payment_method" key to avoid accidental overrides.
🧹 Nitpick comments (29)
src/Sylius/Bundle/AddressingBundle/Resources/translations/messages.ar.yml (2)
15-15: Province Translation Update
Updating “province” to “المقاطعة” incorporates the definite article for clarity. Please verify that this change aligns with the project’s overall localization style.
22-22: Enabled Key Translation Update
The translation forenabledis now “مفعّل.” Note that other bundles (e.g. UserBundle below) use “مفعل.” It might be worth verifying consistency across the project.src/Sylius/Bundle/UserBundle/Resources/translations/messages.ar.yml (1)
8-8: Enabled Key Translation Update
The update to “مفعل” for theenabledfield is acceptable; however, note the difference from “مفعّل” in the AddressingBundle. Consider harmonizing these for consistency across the project.src/Sylius/Bundle/UiBundle/Resources/translations/messages+intl-icu.ar.yml (1)
7-9: Lowest Price Message Formatting and Trailing Spaces
The ICU formatting forlowest_price_days_before_discount_wasis well-structured; however, YAMLlint has flagged trailing spaces on lines 7 and 8. Please remove these extra spaces to maintain clean formatting. Suggested diff:- lowest_price_days_before_discount_was: '{days, plural, - one {أقل سعر من # يوم قبل الخصم الحالي كان {price}} + lowest_price_days_before_discount_was: '{days, plural, + one {أقل سعر من # يوم قبل الخصم الحالي كان {price}}🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 7-7: trailing spaces
(trailing-spaces)
[error] 8-8: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/TaxationBundle/Resources/translations/messages.ar.yml (1)
8-16: Enhanced Tax Rate Terminology
The new and revised keys under thetax_ratesection (amount, calculator, category, end_date, included_in_price, name, start_date) improve clarity and completeness. One minor note: the translation forincluded_in_priceuses a question mark ("مشمول في السعر؟"). Please verify that this punctuation is intentional and consistent with the expected UI context.src/Sylius/Bundle/LocaleBundle/Resources/translations/validators.ar.yml (1)
7-10: Improved Locale Validation Messages
The updated validation messages for locale codes now prompt users to select a proper language code. Consider verifying that there are no unintended leading or trailing spaces (for example, in thenot_blankmessage) and that punctuation is consistent with other validation messages.src/Sylius/Bundle/AddressingBundle/Resources/translations/validators.ar.yml (2)
7-31: Enhanced Address Field Validations
Within thesylius: address:block, the validations for fields such as city, country, first name, last name, postcode, province (validity), street, and the additionalnot_shippablekey have been updated. The use of pipe-separated messages (e.g., formax_lengthandmin_length) appears deliberate for pluralization purposes. Please confirm that the duplicate phrases are intended for singular/plural variations or if a single message would suffice for your localization strategy.
33-37: Country Code and Province Uniqueness Validations
The translations for thesylius: country:block (coveringcodewith not_blank, unique, and an error message under the keycountry, as well asunique_provinces) are clear. One point to check: the keycountryfor the invalid ISO code message might be more intuitive asinvalidor similar. Verify that this naming aligns with your validation message keys elsewhere in the codebase.src/Sylius/Bundle/ShippingBundle/Resources/translations/validators.ar.yml (2)
15-15: Remove Trailing SpacesStatic analysis has flagged trailing spaces at this line. Please remove any excess whitespace to comply with YAML linting rules.
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 15-15: trailing spaces
(trailing-spaces)
34-34: Eliminate Trailing SpacesSimilarly, trailing spaces detected on this line should be removed to maintain clean formatting in the YAML file.
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 34-34: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/ShippingBundle/Resources/translations/messages.ar.yml (1)
10-10: Trailing Whitespace CleanupYAMLlint has flagged trailing spaces on lines 10, 20, 27, and 30. Please remove these extraneous spaces to ensure clean YAML formatting. For example:
- type: نوع القاعدة␣␣ + type: نوع القاعدةAlso applies to: 20-20, 27-27, 30-30
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 10-10: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/TaxationBundle/Resources/translations/validators.ar.yml (1)
15-15: Trailing Whitespace Alert
There are trailing spaces detected on line 15. Removing these will help keep the file clean and in line with YAML lint guidelines.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 15-15: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/AttributeBundle/Resources/translations/validators.ar.yml (4)
7-9: Attribute Name Validation Messages Updated
The updated messages for attribute name validations (for not_blank, min_length, and max_length) are clear and make effective use of singular/plural patterns. Please verify that the dynamic {{ limit }} placeholder values align with the enforced business constraints.
11-15: Attribute Code Validation Messages Updated
The messages for code validations—including min_length, max_length, not_blank, regex, and uniqueness—are precise and informative. Ensure that the regex pattern and length limits perfectly match the validation logic in the backend.
17-20: Configuration Validation Messages Refined
The configuration messages clearly describe the relationship between maximum/minimum entries and lengths. Their wording should help end users understand the constraints without ambiguity.
22-24: Presentation Validation Messages Clarity
The presentation field messages now use a consistent style for not_blank, min_length, and max_length validations. Confirm that these translations integrate smoothly with the UI.src/Sylius/Bundle/CustomerBundle/Resources/translations/validators.ar.yml (4)
7-9: Customer First Name Validations Updated
The first name validations now clearly communicate maximum and minimum length constraints as well as the requirement to provide a value. Ensure the displayed {{ limit }} matches the actual rule.
11-13: Customer Last Name Validations Updated
The last name validations mirror the first name changes and provide clear guidance on length limits and non-emptiness.
17-22: Customer Email Validations Refined
The email field now features detailed messages for already-used emails, maximum/minimum lengths, invalid formats, uniqueness, and even suggests using the “نسيت كلمة المرور” option.
27-30: Customer Group Code Validations Updated
The updates for customer group code validations (max_length, regex, uniqueness, and non-blank) are clear and help ensure consistency with system rules.src/Sylius/Bundle/ProductBundle/Resources/translations/validators.ar.yml (5)
10-12: Slug Validation Messages Updated
The slug validations now include not_blank, unique, and max_length messages. Please double-check that the max_length phrasing (stating a limit of “حرفًا واحدًا” when using {{ limit }}) is intentional and reflects the rule dynamically.
13-17: Product Code Validation Messages Updated
The messages for the product code provide clear instructions regarding maximum length, requirement, regex constraints, and uniqueness. Confirm that the {{ limit }} placeholder is dynamically set to the correct value.
18-21: Product Name Validation Messages Updated
The not_blank, min_length, and max_length validations for the product name are consistent in language and style. Verify that the limits communicated are accurate and meet user expectations.
22-25: Meta Fields Validation Updates
The updated max_length messages for meta keywords and meta description ensure that these fields adhere to defined character limits.
65-69: Association Type Name Validations Updated
The association type name validations now clearly ensure that the name is provided and meets the required length constraints.src/Sylius/Bundle/CoreBundle/Resources/translations/validators.ar.yml (1)
26-39: Catalog Promotion Scope Validations Updated
The validations undercatalog_promotion_scopedetail errors for various subtypes (for_products, for_variants, for_taxons). The language is consistent, though consider reviewing the repeated “تحتوي الإعدادات على أخطاء” phrasing for uniformity.src/Sylius/Bundle/PromotionBundle/Resources/translations/validators.ar.yml (1)
19-19: Trailing Spaces Detected
YAMLlint has flagged the presence of trailing spaces on several lines (specifically on lines 19, 29, 34, 51, 56, 59, and 73). Removing these will help maintain proper YAML formatting standards.Also applies to: 29-29, 34-34, 51-51, 56-56, 59-59, 73-73
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 19-19: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/ShopBundle/Resources/translations/messages.ar.yml (1)
8-8: Remove Trailing Spaces
Static analysis detected trailing spaces on several lines. Please remove extra whitespace on lines 8, 33, 42, 54, 57, and 67 to ensure clean YAML formatting.Also applies to: 33-33, 42-42, 54-54, 57-57, 67-67
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 8-8: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/PromotionBundle/Resources/translations/messages.ar.yml (1)
76-77: Nth Order Configuration Translation
Thenthkey is translated as "الرقم." Consider verifying that this translation clearly conveys the intended meaning (e.g. order sequence) to avoid ambiguity.
📜 Review details
Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro
📒 Files selected for processing (49)
src/Sylius/Bundle/AddressingBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/AddressingBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/AdminBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/AdminBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/AttributeBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/AttributeBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/ChannelBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/ChannelBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/CoreBundle/Resources/translations/flashes.ar.yaml(1 hunks)src/Sylius/Bundle/CoreBundle/Resources/translations/messages.ar.yml(3 hunks)src/Sylius/Bundle/CoreBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/CurrencyBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/CurrencyBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/CustomerBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/CustomerBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/CustomerBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/LocaleBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/LocaleBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/OrderBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/OrderBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/PaymentBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/PaymentBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/PaymentBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/PayumBundle/Resources/translations/messages+intl-icu.ar.yml(1 hunks)src/Sylius/Bundle/PayumBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/PayumBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/ProductBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/ProductBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/ProductBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/PromotionBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/PromotionBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/PromotionBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/ReviewBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/ReviewBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/ReviewBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/ShippingBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/ShippingBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/ShippingBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/ShopBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/TaxationBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/TaxationBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/TaxonomyBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/TaxonomyBundle/Resources/translations/validators.ar.yml(1 hunks)src/Sylius/Bundle/UiBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/UiBundle/Resources/translations/messages+intl-icu.ar.yml(1 hunks)src/Sylius/Bundle/UiBundle/Resources/translations/messages.ar.yml(1 hunks)src/Sylius/Bundle/UserBundle/Resources/translations/flashes.ar.yml(1 hunks)src/Sylius/Bundle/UserBundle/Resources/translations/messages.ar.yml(2 hunks)src/Sylius/Bundle/UserBundle/Resources/translations/validators.ar.yml(1 hunks)
🧰 Additional context used
🪛 YAMLlint (1.35.1)
src/Sylius/Bundle/UiBundle/Resources/translations/messages+intl-icu.ar.yml
[error] 7-7: trailing spaces
(trailing-spaces)
[error] 8-8: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/ShippingBundle/Resources/translations/validators.ar.yml
[error] 15-15: trailing spaces
(trailing-spaces)
[error] 34-34: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/ShippingBundle/Resources/translations/messages.ar.yml
[error] 10-10: trailing spaces
(trailing-spaces)
[error] 20-20: trailing spaces
(trailing-spaces)
[error] 27-27: trailing spaces
(trailing-spaces)
[error] 30-30: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/TaxationBundle/Resources/translations/validators.ar.yml
[error] 15-15: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/PromotionBundle/Resources/translations/validators.ar.yml
[error] 19-19: trailing spaces
(trailing-spaces)
[error] 29-29: trailing spaces
(trailing-spaces)
[error] 34-34: trailing spaces
(trailing-spaces)
[error] 51-51: trailing spaces
(trailing-spaces)
[error] 56-56: trailing spaces
(trailing-spaces)
[error] 59-59: trailing spaces
(trailing-spaces)
[error] 73-73: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/ShopBundle/Resources/translations/messages.ar.yml
[error] 8-8: trailing spaces
(trailing-spaces)
[error] 33-33: trailing spaces
(trailing-spaces)
[error] 42-42: trailing spaces
(trailing-spaces)
[error] 54-54: trailing spaces
(trailing-spaces)
[error] 57-57: trailing spaces
(trailing-spaces)
[error] 67-67: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/CoreBundle/Resources/translations/messages.ar.yml
[error] 279-279: syntax error: expected , but found ''
(syntax)
🪛 GitHub Check: Static checks / PHP 8.3, Symfony ^7.1
src/Sylius/Bundle/CoreBundle/Resources/translations/messages.ar.yml
[failure] 279-279:
Unexpected characters near "Europe/Amsterdam")"" at line 279 (near "timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")"").
🪛 GitHub Check: Static checks / PHP 8.2, Symfony ^6.4
src/Sylius/Bundle/CoreBundle/Resources/translations/messages.ar.yml
[failure] 279-279:
Unexpected characters near "Europe/Amsterdam")"" at line 279 (near "timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")"").
🪛 GitHub Actions: Continuous Integration (Minimal)
src/Sylius/Bundle/CoreBundle/Resources/translations/messages.ar.yml
[error] 279-279: Unexpected characters near "Europe/Amsterdam")" at line 279 (near "timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")").
🔇 Additional comments (237)
src/Sylius/Bundle/ProductBundle/Resources/translations/flashes.ar.yml (1)
6-6: Translation Update for Product Variant Generation Message
The updated value "تم إنشاء متغيرات المنتج بنجاح." is clear and appropriately rephrased, maintaining the intended meaning.src/Sylius/Bundle/LocaleBundle/Resources/translations/messages.ar.yml (1)
8-8: New Locale Selection Prompt Added
The addition of theselect: اختر اللغة...entry under the locale section enhances the language selection experience for Arabic users. It is clear and consistent with the rest of the translations.src/Sylius/Bundle/CustomerBundle/Resources/translations/flashes.ar.yml (1)
6-6: Refinement of Customer Registration Message
The revised translation "شكرًا على التسجيل، تحقق من بريدك الإلكتروني للتحقق من حسابك." offers a more concise and user-friendly message while preserving the original intent.src/Sylius/Bundle/CoreBundle/Resources/translations/flashes.ar.yaml (1)
1-4: New Payment Error Message Introduced
The new translation forcannot_be_completedclearly communicates that a payment cannot be completed due to insufficient stock, using a dynamic placeholder ("%productVariantCode%"). This will help in displaying context-specific error messages consistently.src/Sylius/Bundle/TaxonomyBundle/Resources/translations/messages.ar.yml (1)
8-11: Improved Terminology in Taxon Translations
The refined translations in the taxon block are as follows:
- enabled: Changed to "مفعل" to accurately denote an active state.
- parent: Updated to "الأصل" for better semantic clarity compared to the previous term.
- slug: Modified to "الاسم المختصر" to more clearly indicate its purpose.
These changes improve consistency and clarity across the application’s taxonomy-related messages.src/Sylius/Bundle/ShippingBundle/Resources/translations/flashes.ar.yml (1)
6-6: Verify YAML quoting consistency for the translation string.
The updated message "تم شحن الشحنة بنجاح." is clear and improves specificity. However, note that the removal of quotes may affect string parsing in some YAML processors if special characters or spacing are introduced later. Please ensure that the file’s YAML parser consistently interprets the value as a string.src/Sylius/Bundle/CurrencyBundle/Resources/translations/messages.ar.yml (1)
7-14: Ensure standardized terminology for currency-related keys.
The updates—changing "enabled" to "مفعّل" and revising "source_currency" and "target_currency" to "العملة المصدر" and "العملة الهدف" respectively—enhance clarity and align with the terminology used in other bundles. Double-check that these terms are used consistently across all currency forms in the UI.src/Sylius/Bundle/PayumBundle/Resources/translations/messages+intl-icu.ar.yml (1)
1-4: ICU pluralization message appears correctly formatted.
The new translation employs proper ICU syntax for pluralization, dynamically handling singular and plural cases. Verify that the placeholders (# for the count and {total} for the amount) are correctly populated by the underlying code.src/Sylius/Bundle/ReviewBundle/Resources/translations/flashes.ar.yml (1)
7-8: Updated review flash messages improve clarity.
The revised translations for the "reject" and "wait_for_the_acceptation" keys now provide a more descriptive response. Please confirm that the key names (especially "wait_for_the_acceptation") are consistent with the rest of the system’s translation keys and that the new wording aligns with the intended user experience.src/Sylius/Bundle/ChannelBundle/Resources/translations/messages.ar.yml (1)
7-11: Channel form translations updated for improved readability.
Changing "enabled" to "مفعل" and updating "url" to "الرابط (URL)" clarifies these labels for users. Ensure that these terms match others throughout the project for a consistent user interface.src/Sylius/Bundle/AddressingBundle/Resources/translations/messages.ar.yml (7)
13-13: Postcode Translation Update
The translation for the keypostcodehas been updated to “الرمز البريدي,” which offers a more accurate representation of the postal code in Arabic.
18-18: Add Province Key Update
The keyadd_provincenow uses “إضافة مقاطعة” to clearly indicate the action. This update improves the label clarity in the address form.
25-25: Abbreviation Translation Update
Theabbreviationkey is updated to “الاختصار,” which adds the definite article and improves clarity.
31-31: Type Key Translation Update
“Type” has been updated to “النوع,” aligning well with the intended meaning.
34-34: Province in Types Section
Within thetypesmapping, the value forprovinceis now “المقاطعة.” This is consistent with the earlier update—well done.
36-36: Scope Key Translation Update
The keyscopehas been updated to “النطاق,” which appropriately reflects the concept in Arabic.
38-38: All Key Translation Update
The translation for the keyallis now “الكل,” an accurate term for this use case in selection contexts.src/Sylius/Bundle/OrderBundle/Resources/translations/validators.ar.yml (2)
6-7: Product Variant Validation Message
A new keyproduct_variantwith anot_blankmessage (“لم يتم توفير نوع المنتج.”) has been introduced. This enhances the validation by providing clear feedback when the product variant is missing.
9-10: Quantity Validation Messages Update
The update refines theminvalidation message to “كمية عنصر الطلب لا يمكن أن تكون أقل من 1.” and adds anot_blankmessage (“لم يتم توفير الكمية.”). These changes enhance clarity for order item validations.src/Sylius/Bundle/ReviewBundle/Resources/translations/messages.ar.yml (5)
8-8: Review Comment Key Update
The translation for the keycommentis now “التعليق,” which adds the definite article for improved specificity in the review form.
9-9: Review Header Update
Changing the header from “إضافة تعليق” to “أضف مراجعة” streamlines the prompt and better conveys the intended action.
12-12: Approved Status Translation Update
The update to “معتمد” for theapprovedstatus in the review form is clear and precise.
16-16: Submit Button Translation Update
Updating thesubmitkey to “إرسال” refines the call-to-action text, making it more user-friendly.
17-17: Title Key Translation Update
The revised translation “العنوان” for thetitlekey clearly conveys the intended meaning.src/Sylius/Bundle/UserBundle/Resources/translations/messages.ar.yml (4)
7-7: Email Translation Update
The translation for
11-11: Password Confirmation Label Update
Theconfirmationlabel under the password section is now “تأكيد” instead of “تأكد,” enhancing clarity.
21-21: User Change Password 'New' Label Update
Thenewlabel for the change password form has been updated to “كلمة المرور الجديدة,” which clearly communicates the action.
24-24: User Reset Password 'New' Label Update
Similarly, updating thenewlabel in the reset password section to “كلمة المرور الجديدة” ensures consistency in the password-related forms.src/Sylius/Bundle/CustomerBundle/Resources/translations/messages.ar.yml (5)
8-8: Customer Group Key Update
The keygroupis now translated as “المجموعة,” with the definite article added to enhance clarity.
13-13: Birthday Field Translation Update
Changing the translation forbirthdayto “تاريخ الميلاد” provides a more formal and precise expression compared to “عيد ميلاد.”
14-14: Billing Address Translation Update
The update from “عنوان الفاتورة” to “عنوان الفوترة” may better capture the invoicing context. Please confirm that this terminology is consistent with domain standards.
15-15: Different Shipping Address Entry
Introducing the new keydifferent_shipping_addresswith the value “استخدام عنوان مختلف للشحن؟” expands form options and improves user guidance.
17-17: Newsletter Subscription Update
Updating thesubscribed_to_newsletterkey to “الاشتراك في النشرة الإخبارية” simplifies the phrasing and removes the possessive form, which enhances clarity.src/Sylius/Bundle/ProductBundle/Resources/translations/messages.ar.yml (7)
7-14: Product Field Translations – Consistency and Clarity
The updated Arabic translations for the product fields (e.g., "name", "description", "attributes", "meta_keywords", etc.) now use uniform quotation and terminology. Using "الخصائص" instead of "سمات" and "الرابط الثابت" for "slug" improves clarity.
16-16: Product Variant Name Translation
The translation for the product variant’s name ("الاسم") is straightforward and consistent with other fields.
18-19: Association Type Updates
The modifications for the association type, where "name" remains "الاسم" and "translations" is updated to "الترجمات", provide a clearer description. Please verify that "الترجمات" is the intended term.
21-22: Association Fields Translation
The updates for the association fields – changing "type" to "نوع الرابط" and "product" to "المنتج المرتبط" – enhance contextual clarity.
24-24: Variant Name Consistency
Retaining "الاسم" for the variant field is consistent with similar fields in the file.
26-28: Option Fields Translation
The translations for option-related fields ("name", "position", "values") are clear. "الموضع" and "القيم الممكنة" appropriately convey their meanings.
30-31: Option Value Translations
The clarity of the "add_value" and "value" keys with their Arabic counterparts enhances user understanding.src/Sylius/Bundle/PayumBundle/Resources/translations/messages.ar.yml (3)
7-7: New "use_payum" Key Addition
Introducing the "use_payum" key with the value "استخدام Payum" under gateway_config clearly indicates the intended configuration change.
9-10: Payum Gateway Translation Adjustments
The updated translations for "cash_on_delivery" ("الدفع عند الاستلام") and for "offline" (now "غير متصل (Payum)") are contextually appropriate. Please double-check that the inclusion of "(Payum)" in the offline message is intended for clarity.
12-12: Gateway Factory Translation Update
The revised translation for "offline" under payum_gateway_factory as "غير متصل" aligns well with the rest of the bundle’s terminology.src/Sylius/Bundle/UserBundle/Resources/translations/validators.ar.yml (3)
7-9: Email Validation Messages Reworded
The updated messages now use the more courteous phrasing "من فضلك" (e.g., "من فضلك أدخل بريدك الإلكتروني.") which improves user guidance.
11-13: Plain Password Validation Improvements
Updating the plainPassword messages to a friendlier tone (e.g., "من فضلك أدخل كلمة المرور.") makes the validations clearer and more user-centric.
15-16: Password Length Validation Clarity
The modifications for the password length validations now correctly reference "كلمة المرور" rather than "البريد الإلكتروني," ensuring the message is accurate.src/Sylius/Bundle/UiBundle/Resources/translations/messages+intl-icu.ar.yml (2)
6-6: ICU Pluralization for Item Choice
The ICU message foritem.choiceeffectively handles pluralization. The format{count, plural, =0 {} one {, 1 عنصر} other {, # عناصر}}is correctly specified.
10-10: Customer Orders Pluralization
The message foroverall_this_customer_has_placed_orders_across_all_channels.choiceeffectively utilizes ICU plural rules to differentiate between zero, singular, and plural cases.src/Sylius/Bundle/PromotionBundle/Resources/translations/flashes.ar.yml (2)
6-6: Promotion Coupon Flash Message Update
Changing the message to "تم إنشاء كوبونات الترويج بنجاح." now clearly indicates that promotion coupons have been created rather than merely accepted. Please ensure this aligns with the underlying business logic.
7-8: Catalog Promotion Removal Message Enhancement
The new flash message informing users that the removal process may take time ("تم طلب إزالة الترويج من الكتالوج. قد تستغرق هذه العملية بعض الوقت اعتمادًا على عدد المنتجات المتأثرة.") is clear and sets proper expectations.src/Sylius/Bundle/PaymentBundle/Resources/translations/flashes.ar.yml (1)
6-12: Clear and Accurate Payment Status Translations
The updated Arabic translations for various payment statuses (authorized, cancelled, completed, failed, processing, refunded, unknown) are concise and clear. Please double-check that the tone and terminology align with the rest of the payment UI across the project.src/Sylius/Bundle/OrderBundle/Resources/translations/flashes.ar.yml (1)
6-10: Consistent Cart Notification Updates
The revised messages for cart operations—such as adding items, modification restrictions, recalculation issues, item removal, and cart update confirmations—now consistently use the term "السلة". This consistency should help maintain a unified user experience.src/Sylius/Bundle/AddressingBundle/Resources/translations/validators.ar.yml (3)
39-48: Province Field Validations Refined
Thesylius: province:section now features updated messages for both thecodeandnamefields. The messages are consistent and clear, using the pipe mechanism for pluralization. Please ensure that the duplicate forms are intentional and adhere to your localization guidelines.
49-65: Zone Validation Messages Update
The translations under thesylius: zone:block—including validations for scope, code (with constraints on length, blankness, and allowed characters), type, members, and name—are now more descriptive. The messages clearly specify constraints using placeholders (e.g.,{{ limit }},{{ value }}), which is great. Ensure that the string for thetypekey (with its allowed choices) matches the expected UI display.
66-71: Zone Member Specific Validations
For thesylius: zone_member:section, the message preventing a zone member from being the zone itself is clear. Additionally, validations for the code (max_length, not_blank, regex) and uniqueness are appropriately updated. Confirm that these messages integrate well with any client-side validations already in place.src/Sylius/Bundle/ReviewBundle/Resources/translations/validators.ar.yml (4)
7-7: Clear and Consistent Rephrasing forauthor.already_existsThe updated message
"هذا البريد الإلكتروني مسجل بالفعل، يرجى تسجيل الدخول أو استخدام كلمة المرور المنسية."
is clear and aligns well with common login prompts, ensuring users understand that the email is already in use.
9-9: Improved Clarity incomment.not_blankMessageThe revised translation "يجب ألا يكون تعليق المراجعة فارغاً." succinctly enforces that reviews must include a comment.
11-11: Enhanced Guidance inrating.not_blankMessageThe message "يجب عليك التحقق من تقييم المراجعة." provides a direct instruction regarding review ratings, improving clarity.
13-15: Concise Validation Prompts fortitleFieldsThe updated entries ensure that the review title is not left blank and must adhere to the specified length limits (at least 2 characters and no more than 255 characters). This improves the overall user guidance.
src/Sylius/Bundle/CurrencyBundle/Resources/translations/validators.ar.yml (6)
7-9: Refined Validation for Currency CodeThe messages under
sylius.currency.codehave been updated for clarity:
•not_blank: "يرجى اختيار رمز العملة."
•unique: "يجب أن يكون رمز العملة فريدًا."
•currency: "هذه القيمة ليست رمز عملة صالحًا."
These clear translations correctly communicate the required conditions.
11-11: Clear Prompt for Exchange Rate InputThe message "يرجى إدخال سعر الصرف." immediately informs users to provide the exchange rate, making the field requirement unmistakable.
14-17: Consistent Ratio Validations for Exchange RateThe set of messages for
sylius.exchange_rate.ratio—including "greater_than", "less_than", "invalid", and "not_blank"—uses the placeholder{{ compared_value }}consistently, ensuring that users clearly understand the numeric constraints.
19-19: Accurate Prompt for Source CurrencyThe updated message "يرجى إدخال العملة المصدر التي يُشتق منها سعر الصرف." is descriptive and instructive.
21-21: Precise Instruction for Target CurrencyThe revision "يرجى إدخال العملة الهدف التي يُحدد لها سعر الصرف." clearly directs users to specify the target currency.
22-23: Ensuring Unique and Distinct Currency PairsThe messages
• "يجب أن يكون زوج العملات فريدًا." and
• "يجب أن تكون العملة المصدر مختلفة عن العملة الهدف."
effectively enforce the business rules regarding currency pair uniqueness and distinctness.src/Sylius/Bundle/AttributeBundle/Resources/translations/messages.ar.yml (3)
7-14: Streamlined Translations for Attribute Form FieldsChanges such as:
•add: إضافة
•add_attributes: إضافة السمات
•code: الرمز
•translatable: قابل للترجمة
•translations: الترجمات
•type: النوع
improve clarity and maintain consistent terminology across the attribute form.
16-27: Refined Attribute Type Labels and OptionsUpdates in this section—for example,
•checkbox: خانة اختيار
•configuration: الإعدادات
•float: عدد عشري
•percent: النسبة المئوية
•select: اختيار
•text: نص
•textarea: حقل نصي
•title: أنواع السمات
•validation: التحقق من الصحة
—enhance the terminology and usability of the attribute types.
30-41: Consistent Configuration Translations for Attribute TypesThe updates under
attribute_type_configurationensure that:
• Date/time formats are uniformly labeled as "التنسيق", and
• Selections (with keys likemultiple,values,choose,min, andmax) as well as textual constraints (minandmaxfor text) are clearly translated.
These improvements will help maintain uniform configuration across the system.src/Sylius/Bundle/UiBundle/Resources/translations/messages.ar.yml (2)
4-14: Enhanced Translations for Form ElementsThe changes in the form section—such as updating "password" to "كلمة المرور", adding "notes: 'ملاحظات إضافية'", and revising "tracked" to "متتبع"—are well implemented to ensure consistency with the overall UI terminology.
16-1027: Comprehensive Update of UI TranslationsThe extensive revisions across the
sylius.uisection cover varied elements such as account management, notifications, action labels, and interface prompts. The updates (for example, "account_credentials" now reads "بيانات اعتماد الحساب" and "accepted" becomes "تم القبول") are thorough and should greatly enhance the user experience for Arabic-speaking users.
Please verify that all embedded HTML tags and placeholders (e.g.,%name%) are correctly maintained and consistent with the rest of the application.src/Sylius/Bundle/ShippingBundle/Resources/translations/validators.ar.yml (8)
7-9: Clear Validation for Shipping Category NameThe messages for the shipping category name—defining
max_length,min_length, andnot_blank—are both clear and precise, effectively guiding the user on acceptable input.
11-14: Rigorous Constraints for Shipping Category CodeThe updated entries for the shipping category code (covering
max_length,not_blank,regex, andunique) form a robust validation suite that ensures the input is both formatted correctly and unique.
18-20: Validation for Shipping Method CalculatorThe messages for the calculator settings—including "لا يمكن أن تكون رسوم الشحن أقل من 0.", "يرجى اختيار آلة حساب رسوم الشحن.", and "آلة حساب غير صالحة. الآلات المتاحة: {{ available_calculators }}."—are well defined and guide the user effectively.
22-24: Proper Constraints on Shipping Method NameThe constraints imposed on the shipping method name (using
max_length,min_length, andnot_blank) ensure that the input meets the required standards.
26-29: Structured Validation for Shipping Method CodeThe clearly specified validation messages—including restrictions on length, presence, regex pattern, and uniqueness—provide comprehensive validation for shipping method codes.
31-31: Mandatory Selection for Shipping Method ZoneThe
not_blankvalidation for the shipping method zone ("يرجى اختيار منطقة طريقة الشحن.") is crucial for ensuring that the correct shipping area is specified.
32-33: Validation on Shipping Method Rule TypeThe new entry "نوع قاعدة غير صالح. الأنواع المتاحة: {{ available_rule_types }}." clearly defines acceptable rule types, enhancing the robustness of the validation.
37-37: Essential Check for Shipment’s Shipping MethodThe validation message "يرجى اختيار طريقة الشحن." for the shipment's shipping method is simple and to the point, ensuring that a shipping method is always provided.
src/Sylius/Bundle/PaymentBundle/Resources/translations/messages.ar.yml (4)
7-9: Translation Update for Credit Card FieldsThe Arabic translations for the credit card fields have been updated (e.g. changing "اسم حامل البطاقة" to "اسم صاحب البطاقة" and refining the expiry texts). These changes enhance clarity and align with the desired terminology.
14-14: Translation Update for Payment Status TermsThe updated translations for payment-related keys (such as "amount", "checkout", "authorized", "failed", "pending", "processing", "void", "cancelled", and "refunded") improve consistency and clarity. Please double-check that these new terms are used uniformly across all bundles.
Also applies to: 18-18, 20-21, 23-24, 26-28
31-34: Translation Update for Payment Method SectionThe modifications to keys like "enabled", "instructions", and "position" now reflect a more accurate and modern Arabic phrasing. Great job maintaining a consistent style with the other sections.
35-38: Addition of Gateway Configuration TranslationsIntroducing the new sections for
gateway_configandgateway_factorywith keys such as "type" and "offline" is clear and useful for the payment gateway integration.src/Sylius/Bundle/ShippingBundle/Resources/translations/messages.ar.yml (4)
8-10: Update in Unit Count ConfigurationThe change of the "count" key from "عد" to "العدد" and the update for "type" to "نوع القاعدة" adds clarity to the UI descriptions in the shipping rules configuration.
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 10-10: trailing spaces
(trailing-spaces)
14-19: Shipment States Translation RefinementThe updated translations for shipment states (e.g. "checkout" → "قيد الإعداد", "pending" → "قيد الانتظار", "shipped" → "تم الشحن", "returned" → "تم الإرجاع", and "cancelled" → "تم الإلغاء") are more descriptive and user-friendly.
23-28: Shipping Calculator and Per Unit Rate ConfigurationThe updated labels and keys—switching to terms like "سعر ثابت لكل شحنة" and "المبلغ"—ensure better clarity for end users when configuring shipping rates.
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 27-27: trailing spaces
(trailing-spaces)
29-34: Shipping Method Section UpdatesThe refinements in the shipping method section (with keys such as "name", "enabled", "position", and the new help text under "rules_help") are well articulated. They guide users effectively through shipping method configuration.
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 30-30: trailing spaces
(trailing-spaces)
src/Sylius/Bundle/TaxonomyBundle/Resources/translations/validators.ar.yml (4)
7-10: Refined Validation Messages for Taxon CodeThe updated messages under
sylius.taxon.code(covering maximum length, non-blank, regex, and uniqueness) now offer clearer guidance for users.
12-13: Validation Messages for Taxon NameThe concise and clear messages for the taxon name, including the maximum length and non-blank requirements, are well stated.
15-16: Updated Slug ValidationsThe modifications for the slug fields (non-blank and uniqueness) are consistent with the project's requirements and improve user feedback.
19-20: Taxonomy Name Validation ImprovementsThe updates for the taxonomy name validations are straightforward and ensure that users are properly instructed regarding the maximum length and mandatory nature of the field.
src/Sylius/Bundle/ChannelBundle/Resources/translations/validators.ar.yml (3)
7-10: Channel Code Validation UpdatesThe rewritten messages for the channel code field—including maximum length, non-blank, regex, and uniqueness—are clear and improve the overall validation user experience.
11-13: Channel Name ValidationThe updated
not_blankandmax_lengthmessages for the channel name provide clear instructions. The phrasing is consistent and effective.
14-17: Color and Hostname Length ConstraintsThe application of maximum length restrictions for the
colorandhostnamefields ensures better data quality and is clearly communicated in the translations.src/Sylius/Bundle/PayumBundle/Resources/translations/validators.ar.yml (3)
6-10: Gateway Configuration Validation EnhancementsThe introduction of validations for
invalid_gateway_factory,gateway_name, andfactory_nameclearly enforces the expected configuration rules. The provided messages are precise and helpful.
13-18: PayPal Credentials ValidationsThe updated non-blank messages for PayPal’s password, signature, and username, along with the new non-null check for the sandbox mode, improve configuration feedback for PayPal integration.
21-24: Stripe Credentials ValidationsThe non-blank validations for Stripe’s secret and publishable keys are clearly defined and consistent with the project's style guidelines.
src/Sylius/Bundle/UserBundle/Resources/translations/flashes.ar.yml (1)
6-14: Arabic Translations – Consistent and Clear Update
The updated keys for password reset, email verification, and related user actions are clear and consistent. The revised messages provide better clarity (e.g. distinguishing between "إعادة تعيين" and "تغيير") and correctly communicate the intended actions in Arabic.src/Sylius/Bundle/UiBundle/Resources/translations/flashes.ar.yml (10)
6-6: Channel Deletion Message Update
The revised message on line 6 clearly states that at least one active channel is required. This update improves clarity for end‐users.
8-8: Checkout Completion Error Message Update
The updated error message now appropriately informs the user of an unexpected issue during order completion and advises to try again.
10-11: Contact Request Messages Revision
Both the success and error messages for contact requests now offer clearer guidance. The success message confirms submission, while the error message suggests a retry later.
13-15: Customer-Related Message Updates
The translations for adding an address, impersonation, and setting an address as default now read naturally and clearly inform the user.
17-20: Order-Related Error and Integrity Messages Update
The messages addressing state machine transition errors, promotion eligibility, total integrity, and update errors for orders are all revised for clarity. They now provide consistent instructions for the user.
22-22: Payment State Machine Error Message Revision
The updated message for payment errors now clearly instructs the user to attempt updating the payment again.
24-25: Product-Related Validation Messages
The messages indicating that a product is in use by a promotion rule and the available stock message have been updated for clarity and precision.
27-27: Product Variant Update Error Message
The revised error message for updating product variants is clear and directs the user to retry the update in case of an issue.
29-29: Promotion Rules Update Message
The new message clearly informs the user that some promotion rules have been updated, with the placeholder for codes intact.
31-32: Taxon Deletion and Usage Message Updates
The updated messages for taxon deletions properly warn the user when a taxon is in use and provide clear instructions regarding menu taxon deletion.src/Sylius/Bundle/TaxationBundle/Resources/translations/validators.ar.yml (9)
7-9: Tax Category Name Validations Update
The revised messages for the tax category name field now require that the name is not blank and provide both minimum and maximum length hints. Ensure that the phrasing (e.g. "حرفًا واحدًا") correctly reflects the intended limits in your business logic.
11-14: Tax Category Code Validations Update
The changes provide clear instructions for the tax category code (max length, not blank, regex, uniqueness). These validations are now more user-friendly and precise.
18-18: Tax Rate Category Not Blank Message
The updated message for selecting a tax rate category is clear and concise.
20-22: Tax Rate Name Validations Update
The not_blank, minimum, and maximum length messages provide helpful feedback for entering the tax rate name. They maintain consistency with the tax category validations.
24-25: Tax Rate Amount Validations Update
The updated messages for tax rate amount now clearly inform the user about invalid values and the requirement to enter a value.
27-27: Tax Rate Calculator Validation
The not_blank message for the tax rate calculator has been updated to clearly instruct the user to choose a tax calculator.
29-29: Tax Rate Zone Validation Update
The updated message for the tax rate zone is succinct and correctly instructs the user to make a selection.
31-34: Tax Rate Code Validations Update
The updated messages for the tax rate code ensure users are informed about the maximum length, non-blank, regex format, and uniqueness criteria.
36-36: Tax Rate Date Validation Addition
Introducing the "greater_than_start_date" validation clarifies that the tax rate’s end date must not precede its start date.src/Sylius/Bundle/AdminBundle/Resources/translations/flashes.ar.yml (4)
5-10: Admin Section Translation Updates
The new entries under the "admin" key (request_reset_password and password_reset messages) provide clear guidance regarding password reset procedures, including success feedback and token expiration. The language is precise and consistent with the rest of the localization effort.
11-13: Email Confirmation Resend Messages
The messages for order and shipment confirmation resends are concise and clearly communicate that the action has been successful.
15-15: Product Variant Generation Message Update
The revised message for product variant generation prevents potential confusion by specifying that variants cannot be created for products lacking option values.
16-19: Locale Deletion Messages Update
The messages under the locale section now clearly state the success condition and the warning when a language is in use, ensuring users understand the constraints.src/Sylius/Bundle/PaymentBundle/Resources/translations/validators.ar.yml (8)
7-8: Credit Card – Cardholder Name Validations Update
The messages requiring a minimum length and non-blank input for the cardholder's name are now more explicit, providing clear feedback when the input is insufficient.
10-12: Credit Card – Expiry Month Validations Update
The updated messages set proper boundaries for the expiry month and ensure that a selection is made. These validations will help prevent input errors.
14-15: Credit Card – Number Validations Update
The not_blank and Luhn algorithm validation messages for the card number now clearly inform the user of format issues.
17-19: Credit Card – Security Code Validations Update
The messages for the security code (CVV) now specify both the requirement and the acceptable numeric length.
21-21: Credit Card – Expiry Year Validation Update
The not_blank validation for the expiry year ensures that users are prompted to select a year, maintaining consistency with other fields.
23-27: Gateway Configuration Validations Update
The new validation messages for gateway configuration (invalid_gateway_factory, gateway_name, and factory_name) clearly guide the user to provide the necessary details for payment processing setups.
29-32: Payment Method – Basic Payment Fields Update
The updated "currency_code" field and the not_blank validation for the payment method ("method") are now more precise, ensuring that the payment inputs meet validation requirements.
33-47: Payment Method – Descriptive Information and Fee Configuration
The validations under the first "payment_method" block (gateway, name, and fee_calculator_configuration) now include clear instructions regarding maximum and minimum lengths and non-blank requirements, which should aid in form validation.src/Sylius/Bundle/AttributeBundle/Resources/translations/validators.ar.yml (1)
29-31: Attribute Value Validation Messages Updated
The messages for attribute value validations, both for selecting the attribute and entering its value, are straightforward and consistent with the overall terminology.src/Sylius/Bundle/CustomerBundle/Resources/translations/validators.ar.yml (3)
15-15: Gender Field Validation Message Updated
The updated message for the gender field (“يرجى اختيار الجنس”) is concise and user friendly.
23-24: Phone Number Validation Message Updated
The revised max_length message for phone numbers is succinct and conforms to the new style guidelines.
31-34: Customer Group Name Validations Updated
The validations for customer group names now include clear messages for maximum, minimum, and required fields.src/Sylius/Bundle/ProductBundle/Resources/translations/validators.ar.yml (12)
7-8: SKU Validation Message Updates
The SKU validations now state that SKU cannot be blank and must be unique. These messages are clear; just ensure that any backend constraints mirror these translations.
26-27: Product Variant Combination Message
The message under “combination” informs users that a variant with the specified option combination already exists. This clarity should improve error reporting.
28-33: Product Variant Code Validations Updated
The validations for product variant codes now cover max_length, not_blank, regex constraints, overall uniqueness, and within-product uniqueness. These messages are comprehensive and well structured.
34-35: Option Values Configuration Validation
The non-configuration validation for option values is now explicit. This message helps ensure that all selected options have defined values.
37-38: Simple Product Code Uniqueness Validation
The uniqueness validation for simple product codes is clearly stated, emphasizing that the code must be unique among all products and variants.
40-44: Product Option Code Validations Updated
The updated messages for product option codes specify maximum length, presence, proper formatting through regex, and uniqueness. They provide comprehensive user guidance.
45-48: Product Option Name Validations Updated
The validations for option names now ensure the value is provided and meet length constraints, making the error messages uniform with other fields.
49-50: Option Values Count Validation Updated
The validation for a minimum count of option values now clearly instructs the user to add at least one (or the required number via {{ limit }}) option value.
52-56: Option Value Code Validations Updated
The messages for option value codes now cover max_length, not_blank, regex, and uniqueness consistently.
57-58: Option Value Field Validation
The not_blank validation for the option’s value is straightforward and clear.
59-64: Association Validations Updated
The validations concerning association uniqueness, type, and owner are now explicitly defined and provide effective user feedback.
70-75: Association Type Code Validations Updated
The messages for association type code validations cover all essential points: minimum and maximum lengths, required presence, allowed characters (via regex), and uniqueness.src/Sylius/Bundle/CoreBundle/Resources/translations/validators.ar.yml (36)
4-11: Admin Password Reset Request Email Validations
The new messages underadmin.password_reset_request.emailclearly indicate invalid formats, length requirements, and the need for a value. Their structure aligns with other translation files.
12-17: Admin Reset Password Validations
The reset password validations now provide clear feedback for password mismatch and detailed requirements (min, max, and required values). This hierarchy improves clarity.
18-21: Avatar Image File Validations Updated
The avatar image file validations for max_size and upload_ini_size are now informative, using dynamic placeholders for size and limit.
22-25: Catalog Promotion Action Fixed Discount Validations
The messages undercatalog_promotion_action.fixed_discountinform the user when channel settings are missing and when the provided discount value is invalid.
41-57: Channel Configuration Validations Updated
The channel section now contains comprehensive validations for base_currency, default_locale, contact_email (with invalid, max, min, and not_blank), contact_phone_number, theme_name, and tax_calculation_strategy. These messages are clear and consistent.
58-61: Channel Price History Config Validations Updated
The messages for price history configuration effectively use dynamic placeholders to specify the required boundaries.
62-68: Channel Pricing Validations Updated
The validations clearly indicate missing channel codes and price constraints (with a check that price is not below zero). Confirm that the uniqueness message corresponds with the underlying logic.
69-70: Channel Code Collection Validation Updated
The error message for an invalid channel code is concise and informative.
71-77: Checkout Validations Updated
The checkout section now addresses CSRF errors (in addressing), missing shipping methods, and restrictions on changing email after login. These messages provide clear user guidance.
78-83: Contact Form Validations Updated
The validations for contact email and message fields now ensure that users provide the necessary information, enhancing clarity.
84-86: Country Code Validation Updated
The message clearly informs the user when a provided country code does not exist.
87-89: Currency Configuration Validation Updated
The validation preventing disabling of the base currency is clear and aligns with business rules.
90-92: Customer Currency Code Validation Updated
The error message for an invalid customer currency code is straightforward.
92-94: Customer Group Validation Updated
The message for a non-existent customer group code is concise and clear.
95-101: Cart Item Validations Updated
The error messages for cart items—including availability, insufficient stock, quantity range, and variant availability—are well articulated and use dynamic placeholders where needed.
102-102: Max Integer Validation Updated
The max_integer message is succinct and correctly uses the {{ compared_value }} placeholder.
103-112: Order Validations Updated
The order validations now cover a range of conditions (address requirements, currency code validity, state transitions, payment method, product and shipping eligibility, and immutability of cart items) with detailed, dynamic messages.
113-116: Resend Confirmation Email Validations Updated
The validations for resending order and shipment confirmation emails clearly indicate when the request is invalid due to the current state.
117-120: Locale Configuration Validation Updated
The message for not disabling the base locale is precise and clear.
121-125: Product Validations Updated
The validations for product variants (ensuring all prices are defined) and for verifying product existence are now explicitly stated.
125-127: Product Attribute Validation Updated
The error message for an invalid product attribute (non-integer order) is clear and succinct.
128-136: Image and Product Image Validations Updated
The messages concerning allowed MIME types, maximum file sizes, and upload size limitations are consistent and help reduce user confusion regarding image uploads. Additionally, the product variant ownership message is explicit.
137-142: Product Taxon Validations Updated
The validations ensuring product taxon uniqueness and non-blank selections for product and taxon are clear.
142-148: Product Variant Validations Updated
The validations for product variant existence and onHand quantity (including reserved quantity checks) offer clear guidance.
149-162: Product Variant Price and Dimension Validations Updated
The messages for original_price, weight, width, height, and depth ensure non-negative values and proper type validation, using dynamic placeholders where applicable.
163-167: Product Variant Channel Pricing Validations Updated
The messages now clearly indicate when a price is not defined or when a channel code is invalid for a product variant.
168-170: Promotion Coupon Validations Updated
The validation for per-customer usage limits now informs users of the minimum threshold required.
171-173: Product Translation Validations Updated
The max_length constraint for product short descriptions is clear and uses dynamic placeholders effectively.
174-176: Province Code Validation Updated
The message for a non-existent province code is clear and straightforward.
177-184: Review Validations Updated
The validations for review author, product, and rating (including range requirements) are clear and enforce proper input conditions.
185-187: Taxon Validation Updated
The error message for a non-existent taxon code succinctly informs the user of the issue.
188-191: Taxon Image Validations Updated
The validations for taxon image file size and upload limits are clearly articulated, with dynamic placeholders ensuring flexibility.
192-198: Translation Validations Updated
The validations regarding translation locales and locale codes now provide clear error messages, ensuring that only supported languages are accepted.
199-212: User Validations Updated
The updated validations for user email, username, and name (including uniqueness and length constraints) are comprehensive and coherent with the overall style.
213-214: User Locale Code Validation Updated
The message for a missing locale code in user settings is clear and direct.
215-217: Zone Validation Updated
The error message for an unrecognized zone code is concise and clearly communicates the issue.src/Sylius/Bundle/PromotionBundle/Resources/translations/validators.ar.yml (12)
5-10: Catalog Promotion Validations Updated
The updated messages undercatalog_promotion(covering code, date, name, and state) use dynamic placeholders effectively and provide clear guidance for valid promotion entries.
11-18: Catalog Promotion Details Validation
The messages for date and name validations, along with the processing state restriction, clearly instruct users on how to correctly configure a catalog promotion.
20-28: Catalog Promotion Action Validations Updated
The validations for promotion actions include clear requirements for the action type and percentage discount (with range and format checks).
30-34: Catalog Promotion Scope Validations Updated
The scope validations now require a chosen type and provide specific error messages if an invalid type is provided.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 34-34: trailing spaces
(trailing-spaces)
35-50: Promotion Validations Updated
The messages for promotion code, description, end date constraints, and overall validity are comprehensive. The dynamic placeholders help tailor error messages to specific limits.
52-56: Promotion Action Validations Updated
The updated promotion action messages clearly specify errors for invalid action types and misconfigured percentage discounts.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 56-56: trailing spaces
(trailing-spaces)
57-59: Promotion Rule Validation Updated
The singular error message for an invalid promotion rule type is clear and concise.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 59-59: trailing spaces
(trailing-spaces)
60-67: Promotion Coupon Validations Updated
The coupon code validations comprehensively cover maximum/minimum length, required fields, regex constraints, and uniqueness, ensuring that coupon inputs adhere to strict guidelines.
68-70: Promotion Coupon Associated Promotion Validations
The messages ensure that a valid associated promotion is provided and that only coupon-based promotions can include coupons.
71-73: Promotion Coupon Usage Limit Validation
The validation for usage limits mandates a minimum value, which helps prevent misconfigurations.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 73-73: trailing spaces
(trailing-spaces)
74-83: Promotion Coupon Generator Instruction Validations Updated
The generator instructions now include comprehensive validations for the number of coupons to generate, code length, and a detailed message explaining possible generation amounts using dynamic placeholders.
84-86: Generated Coupon Usage Limit Validation
The final usage limit for generated coupons is clearly stated and uses the dynamic {{ limit }} placeholder appropriately.src/Sylius/Bundle/ShopBundle/Resources/translations/messages.ar.yml (10)
5-7: New Account Translation Keys Added
The new keys undersylius.account(e.g.dont_have_an_accountandregister_here) are clear and consistent with the project’s tone.
11-15: Order Confirmation Translation Enhancements
The updated order confirmation messages (includinghas_been_successfully_placed,subject,view_order_or_change_payment_method,thank_you, andyour_order_number) provide clear and user-friendly instructions.
17-22: Password Reset Translation Updates
The translations undersylius.email.password_resetare comprehensive and give clear guidance for resetting passwords.
24-27: User Registration Translation Updates
The keys insylius.email.user_registration(e.g.start_shopping,subject,welcome_to_our_store, andyou_have_just_been_registered) are well translated and consistent with the overall UI language.
29-32: Verification Token Translation Refinement
The translations forsylius.email.verification_tokennow clearly communicate the verification process.
34-41: Footer Banner Translation Enhancements
The new footer banner keys (includingfree_shipping_title,free_shipping_content,guarantee_title,guarantee_content,multiple_payments_title, andmultiple_payments_content) improve clarity in the store’s footer.
43-53: Homepage Translation Updates
The homepage keys (such asabout_us,about_us_content,banner_content,banner_button,carousel_header,latest_deals,new_collection,newsletter,newsletter_description, andsubscribe) are thoroughly updated. Please double-check that any embedded HTML (e.g. inabout_us_contentandnewsletter_description) renders correctly on all target devices.
56-57: Lightbox Translation Key
The translation forimage_album_labelin thesylius.lightboxsection correctly uses placeholders for dynamic content.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 57-57: trailing spaces
(trailing-spaces)
61-67: Shop Account Translation Updates
The keys undersylius.menu.shop.account(likeaddress_book,change_password,dashboard,header,order_history, andpersonal_information) are consistent and clear.🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 67-67: trailing spaces
(trailing-spaces)
68-68: Top Bar Translation Update
The top bar message offers a clear call-to-action regarding newsletter subscription and discount information.src/Sylius/Bundle/CoreBundle/Resources/translations/messages.ar.yml (11)
5-12: Admin Password Reset Translations
The keys withinsylius.email.admin_password_reset(fromhellototoken) are clear and provide proper instruction for password resets for administrators.
13-16: Contact Request Translations
The new contact request keys (content,message_from, andsubject) are succinct and appropriate.
17-22: Order Confirmation Email Translations
The order confirmation messages are well refined and consistent with the language style used elsewhere in the project.
23-29: Password Reset Email Translations
The password reset section now clearly outlines the necessary instructions and tokens for end users.
30-35: Shipment Confirmation Email Translations
The shipment confirmation messages are detailed—including placeholder usage for the tracking code—and are well written.
36-40: User Registration Email Translations
The keys undersylius.email.user_registrationare comprehensive and mirror the translations in the ShopBundle for consistency.
41-47: Verification Token Translations
Although noted as deprecated, the translations forverification_tokenare complete and consistent with related messages.
48-54: User Account Verification Translations
The updates undersylius.email.user.account_verificationare accurate and clear.
56-222: Form Section Translations Overview
Thesylius.formsection now includes a wide range of keys (from block, cart, catalog_promotion, checkout, currency, promotion, product, etc.) that are thoroughly updated. Please verify that all dynamic placeholders and descriptions match their intended usage in the application.
223-263: Installer Translations and File System Help Texts
The new translations for the installer (covering extensions, cache, logs, parameters, and vendors) provide detailed guidance. Ensure these instructions remain clear to end users configuring the system.
287-289: Shipping Method Resolver Translation
The translation forby_zones_and_channelis succinct and appropriate.src/Sylius/Bundle/PromotionBundle/Resources/translations/messages.ar.yml (17)
7-9: Catalog Promotion Action Translations
The new keys undercatalog_promotion.action—defining bothfixed_discountandpercentage_discount—are clearly differentiated. Verify that the phrase for percentage discounts (“خصم نسبي (بالنسبة المئوية)”) is consistent with terminology used elsewhere.
11-13: Catalog Promotion General Translations
The translations forenabled,end_date, andlabelare appropriately updated. Consistency with similar keys in other bundles is maintained.
16-17: Catalog Promotion Date and Translations Block
The keys forstart_dateandtranslationsare correctly added and match the overall style.
19-21: Promotion Section Translations (Actions and Rules)
The updates foractionsandadd_actionin the promotion section are clear. Additionally, the inclusion ofadd_ruleis consistent with the UI terminology.
22-24: Promotion Discount Application Translations
The new keysapplies_to_discountedandapplies_to_discounted_detailsprovide useful descriptive text, whilecoupon_basedhas been retained with its translation.
26-33: Promotion Additional Translations
The keysends_at,exclusive,label,name,priority,rules,starts_at, andusage_limitare translated clearly and maintain consistency with other promotion interfaces.
34-45: Promotion Action Details
The translations related to promotion actions—including item and order discount types and shipping percentage discount—are appropriately specific. The sub-configurations (for fixed and percentage discounts) are also clear.
46-48: Promotion Coupon Translations
The keys for coupon expiry (expires_at) and usage limits are precise and consistent with similar translations in other parts of the system.
49-55: Promotion Coupon Generator Instructions
The instructions for the coupon generator (includingamount,code_length,expires_at,prefix,suffix, andusage_limit) are clearly articulated.
56-57: Promotion Filter Translation Update
The translation forprice_rangeis concise and clear.
58-64: Promotion Rule Translations
The newly added keys (such ascart_quantity,contains_product,customer_group,has_at_least_one_from_taxons, anditem_total) accurately describe promotion conditions.
65-67: Promotion Rule Additional Keys
The translation fortotal_price_of_items_from_taxonis correct and further clarifies the promotion rule’s requirement.
68-70: Cart Quantity Configuration Translations
The keys undercart_quantity_configuration(includingcountandequal) are correctly translated.
71-73: Contains Product Configuration
The addition ofexcludein thecontains_product_configurationblock is a useful clarification.
74-75: Item Total Configuration Translation
The configuration keyamountis clearly translated for item totals.
78-80: Shipping Country Configuration
The translation for the shipping country configuration is straightforward and clear.
81-83: Taxonomy Configuration Translations
The keys for excluding taxons and specifyingtaxonsandtypeare appropriately translated.src/Sylius/Bundle/AdminBundle/Resources/translations/messages.ar.yml (7)
5-11: Shipment Confirmation Email Translations
The updated keys insylius.email.shipment_confirmation(includinghas_been_sent_using,subject,thank_you_for_transaction,you_can_check_its_location_with_the_tracking_code, andyour_order_with_number) are consistent and improve the clarity of shipment notifications.
12-20: Admin Form Translations: Channel & Reset Password
The translations undersylius.form.admin—covering channel information (e.g.lowest_price_for_discounted_products_visibleandperiod_for_which_the_lowest_price_is_calculated) and the reset password section (labelandconfirmation)—are well written and clear.
21-31: Admin Menu – Catalog Translations
The catalog section within the admin main menu now uses updated keys such asassociation_types,attributes,header,inventory, andtaxons. These translations are appropriately refined.
32-41: Admin Menu – Configuration Translations
The configuration block now features updated keys (includingadmin_users,countries,exchange_rates,header, andlocales) that align with current terminology.
46-51: Admin Menu – Marketing Translations
The marketing section now reflects updated translations forcart_promotions,catalog_promotions,product_reviews, andpromotions.
52-66: Admin Menu – Customers, Sales & Official Support Translations
The groups under customers, sales, and official support (including labels likecustomers,groups,header,orders, and support-related keys) are updated in a clear and consistent manner.
67-127: User Interface (UI) Translations Enhancements
A comprehensive update of the UI translations now covers a wide range of keys—from basic elements likeaccount,admin_user,add_new_entry, andback_to_dashboardto detailed messages for promotions, pricing, notifications, and search. These changes enhance clarity and usability. Please recheck long descriptive texts (e.g. forminimum_price_detailsandoriginal_price_details) to ensure they communicate their intent effectively.
| type: | ||
| unregistered: نوع السمة "%type%" غير مسجل. | ||
| unregistered: 'نوع السمة "%type%" غير مسجّل. الأنواع المتاحة: %available_types%.' |
There was a problem hiding this comment.
🛠️ Refactor suggestion
New Attribute Type Message Added
Adding an error message for unregistered attribute types is a valuable improvement. The message clearly informs the user about invalid types and lists available ones using placeholders.
| settings: | ||
| header: إصدار PHP والإعدادات | ||
| any: أي | ||
| detect_unicode: detect_unicode | ||
| detect_unicode_help: تعيين 'detect_unicode = Off' في ملف php.ini | ||
| detect_unicode_help: عيّن 'detect_unicode = Off' في ملف php.ini الخاص بك | ||
| magic_quotes_gpc: magic_quotes_gpc | ||
| non_deprecated: غير مهمل | ||
| off: إيقاف | ||
| on: تشغيل | ||
| non_deprecated: غير مهملة | ||
| off: معطّل | ||
| on: مفعّل | ||
| register_globals: register_globals | ||
| session: | ||
| auto_start: session.auto_start | ||
| auto_start_help: تعيين 'session.auto_start = Off' في ملف php.ini | ||
| auto_start_help: عيّن 'session.auto_start = Off' في ملف php.ini الخاص بك | ||
| short_open_tag: short_open_tag | ||
| timezone: المنطقة الزمنية | ||
| timezone_help: تعيين 'date.timezone' في ملف php.ini (مثل date.timezone = "Europe/Amsterdam") | ||
| timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")" | ||
| timezone_deprecated: | ||
| header: المنطقة الزمنية المهملة | ||
| help: المنطقة الزمنية %timezone% مهملة. يرجى إصلاح ملف php.ini (قائمة المناطق الزمنية المهملة http://php.net/manual/en/timezones.others.php). | ||
| version: إصدار PHP | ||
| header: منطقة زمنية مهملة | ||
| help: "مهمة. عدل ملف php.ini الخاص بك (%timezone% المنطقة الزمنية المهملة). http://php.net/manual/en/timezones.others.php" | ||
| version: إصدار PHP | ||
| version_recommended: إصدار PHP الموصى به | ||
| version_help: Sylius يوصي بإصدار PHP %recommended%، والإصدار الحالي لديك هو %current%. يرجى التحديث. | ||
|
|
||
| payum_gateway: | ||
| cash_on_delivery: الدفع عند الاستلام | ||
| offline: غير متصل | ||
| paypal_express_checkout: PayPal Express Checkout | ||
| version_help: يوصي Sylius باستخدام إصدار PHP %recommended%، والإصدار الحالي هو %current%. يُرجى التحديث. | ||
|
|
There was a problem hiding this comment.
Settings Translations Consistency & YAML Syntax Issue
The settings block is comprehensive; however, note the following critical YAML syntax error:
- YAML Syntax Error on Line 279: The key
timezone_helpuses a double-quoted string that contains unescaped inner double quotes around Europe/Amsterdam. This causes a parsing error. Please resolve by either escaping the inner quotes or switching the outer quotes to single quotes. For example:
- timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")"
+ timezone_help: 'عيّن "date.timezone" في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")'📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| settings: | |
| header: إصدار PHP والإعدادات | |
| any: أي | |
| detect_unicode: detect_unicode | |
| detect_unicode_help: تعيين 'detect_unicode = Off' في ملف php.ini | |
| detect_unicode_help: عيّن 'detect_unicode = Off' في ملف php.ini الخاص بك | |
| magic_quotes_gpc: magic_quotes_gpc | |
| non_deprecated: غير مهمل | |
| off: إيقاف | |
| on: تشغيل | |
| non_deprecated: غير مهملة | |
| off: معطّل | |
| on: مفعّل | |
| register_globals: register_globals | |
| session: | |
| auto_start: session.auto_start | |
| auto_start_help: تعيين 'session.auto_start = Off' في ملف php.ini | |
| auto_start_help: عيّن 'session.auto_start = Off' في ملف php.ini الخاص بك | |
| short_open_tag: short_open_tag | |
| timezone: المنطقة الزمنية | |
| timezone_help: تعيين 'date.timezone' في ملف php.ini (مثل date.timezone = "Europe/Amsterdam") | |
| timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")" | |
| timezone_deprecated: | |
| header: المنطقة الزمنية المهملة | |
| help: المنطقة الزمنية %timezone% مهملة. يرجى إصلاح ملف php.ini (قائمة المناطق الزمنية المهملة http://php.net/manual/en/timezones.others.php). | |
| version: إصدار PHP | |
| header: منطقة زمنية مهملة | |
| help: "مهمة. عدل ملف php.ini الخاص بك (%timezone% المنطقة الزمنية المهملة). http://php.net/manual/en/timezones.others.php" | |
| version: إصدار PHP | |
| version_recommended: إصدار PHP الموصى به | |
| version_help: Sylius يوصي بإصدار PHP %recommended%، والإصدار الحالي لديك هو %current%. يرجى التحديث. | |
| payum_gateway: | |
| cash_on_delivery: الدفع عند الاستلام | |
| offline: غير متصل | |
| paypal_express_checkout: PayPal Express Checkout | |
| version_help: يوصي Sylius باستخدام إصدار PHP %recommended%، والإصدار الحالي هو %current%. يُرجى التحديث. | |
| settings: | |
| header: إصدار PHP والإعدادات | |
| any: أي | |
| detect_unicode: detect_unicode | |
| detect_unicode_help: عيّن 'detect_unicode = Off' في ملف php.ini الخاص بك | |
| magic_quotes_gpc: magic_quotes_gpc | |
| non_deprecated: غير مهملة | |
| off: معطّل | |
| on: مفعّل | |
| register_globals: register_globals | |
| session: | |
| auto_start: session.auto_start | |
| auto_start_help: عيّن 'session.auto_start = Off' في ملف php.ini الخاص بك | |
| short_open_tag: short_open_tag | |
| timezone: المنطقة الزمنية | |
| timezone_help: 'عيّن "date.timezone" في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")' | |
| timezone_deprecated: | |
| header: منطقة زمنية مهملة | |
| help: "مهمة. عدل ملف php.ini الخاص بك (%timezone% المنطقة الزمنية المهملة). http://php.net/manual/en/timezones.others.php" | |
| version: إصدار PHP | |
| version_recommended: إصدار PHP الموصى به | |
| version_help: يوصي Sylius باستخدام إصدار PHP %recommended%، والإصدار الحالي هو %current%. يُرجى التحديث. |
🧰 Tools
🪛 YAMLlint (1.35.1)
[error] 279-279: syntax error: expected , but found ''
(syntax)
🪛 GitHub Check: Static checks / PHP 8.3, Symfony ^7.1
[failure] 279-279:
Unexpected characters near "Europe/Amsterdam")"" at line 279 (near "timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")"").
🪛 GitHub Check: Static checks / PHP 8.2, Symfony ^6.4
[failure] 279-279:
Unexpected characters near "Europe/Amsterdam")"" at line 279 (near "timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")"").
🪛 GitHub Actions: Continuous Integration (Minimal)
[error] 279-279: Unexpected characters near "Europe/Amsterdam")" at line 279 (near "timezone_help: "عيّن 'date.timezone' في ملف php.ini (مثال: date.timezone = "Europe/Amsterdam")").
8922c4c to
c888754
Compare
Summary by CodeRabbit