@hyper.software/visitor-common-translations 2.0.84 → 2.0.86
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +93 -93
- package/lib/translations/locale/locale.de-DE.json +2 -1
- package/lib/translations/locale/locale.en-US.json +2 -1
- package/lib/translations/locale/locale.es-ES.json +2 -1
- package/lib/translations/locale/locale.fr-FR.json +2 -1
- package/lib/translations/locale/locale.it-IT.json +2 -1
- package/lib/translations/locale/locale.ro-RO.json +2 -1
- package/package.json +70 -70
package/README.md
CHANGED
|
@@ -1,93 +1,93 @@
|
|
|
1
|
-
# vz-common-translations
|
|
2
|
-
|
|
3
|
-
|
|
4
|
-
|
|
5
|
-
## Getting started
|
|
6
|
-
|
|
7
|
-
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
|
|
8
|
-
|
|
9
|
-
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
|
|
10
|
-
|
|
11
|
-
## Add your files
|
|
12
|
-
|
|
13
|
-
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
|
|
14
|
-
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
|
|
15
|
-
|
|
16
|
-
```
|
|
17
|
-
cd existing_repo
|
|
18
|
-
git remote add origin https://gitlab.com/vz-web/vz-common-translations.git
|
|
19
|
-
git branch -M main
|
|
20
|
-
git push -uf origin main
|
|
21
|
-
```
|
|
22
|
-
|
|
23
|
-
## Integrate with your tools
|
|
24
|
-
|
|
25
|
-
- [ ] [Set up project integrations](https://gitlab.com/vz-web/vz-common-translations/-/settings/integrations)
|
|
26
|
-
|
|
27
|
-
## Collaborate with your team
|
|
28
|
-
|
|
29
|
-
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
|
|
30
|
-
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
|
|
31
|
-
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
|
|
32
|
-
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
|
|
33
|
-
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
|
|
34
|
-
|
|
35
|
-
## Test and Deploy
|
|
36
|
-
|
|
37
|
-
Use the built-in continuous integration in GitLab.
|
|
38
|
-
|
|
39
|
-
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
|
|
40
|
-
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
|
|
41
|
-
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
|
|
42
|
-
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
|
|
43
|
-
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
|
|
44
|
-
|
|
45
|
-
***
|
|
46
|
-
|
|
47
|
-
# Editing this README
|
|
48
|
-
|
|
49
|
-
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
|
|
50
|
-
|
|
51
|
-
## Suggestions for a good README
|
|
52
|
-
|
|
53
|
-
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
|
|
54
|
-
|
|
55
|
-
## Name
|
|
56
|
-
Choose a self-explaining name for your project.
|
|
57
|
-
|
|
58
|
-
## Description
|
|
59
|
-
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
|
|
60
|
-
|
|
61
|
-
## Badges
|
|
62
|
-
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
|
|
63
|
-
|
|
64
|
-
## Visuals
|
|
65
|
-
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
|
|
66
|
-
|
|
67
|
-
## Installation
|
|
68
|
-
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
|
|
69
|
-
|
|
70
|
-
## Usage
|
|
71
|
-
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
|
|
72
|
-
|
|
73
|
-
## Support
|
|
74
|
-
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
|
|
75
|
-
|
|
76
|
-
## Roadmap
|
|
77
|
-
If you have ideas for releases in the future, it is a good idea to list them in the README.
|
|
78
|
-
|
|
79
|
-
## Contributing
|
|
80
|
-
State if you are open to contributions and what your requirements are for accepting them.
|
|
81
|
-
|
|
82
|
-
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
|
|
83
|
-
|
|
84
|
-
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
|
|
85
|
-
|
|
86
|
-
## Authors and acknowledgment
|
|
87
|
-
Show your appreciation to those who have contributed to the project.
|
|
88
|
-
|
|
89
|
-
## License
|
|
90
|
-
For open source projects, say how it is licensed.
|
|
91
|
-
|
|
92
|
-
## Project status
|
|
93
|
-
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
|
|
1
|
+
# vz-common-translations
|
|
2
|
+
|
|
3
|
+
|
|
4
|
+
|
|
5
|
+
## Getting started
|
|
6
|
+
|
|
7
|
+
To make it easy for you to get started with GitLab, here's a list of recommended next steps.
|
|
8
|
+
|
|
9
|
+
Already a pro? Just edit this README.md and make it your own. Want to make it easy? [Use the template at the bottom](#editing-this-readme)!
|
|
10
|
+
|
|
11
|
+
## Add your files
|
|
12
|
+
|
|
13
|
+
- [ ] [Create](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#create-a-file) or [upload](https://docs.gitlab.com/ee/user/project/repository/web_editor.html#upload-a-file) files
|
|
14
|
+
- [ ] [Add files using the command line](https://docs.gitlab.com/ee/gitlab-basics/add-file.html#add-a-file-using-the-command-line) or push an existing Git repository with the following command:
|
|
15
|
+
|
|
16
|
+
```
|
|
17
|
+
cd existing_repo
|
|
18
|
+
git remote add origin https://gitlab.com/vz-web/vz-common-translations.git
|
|
19
|
+
git branch -M main
|
|
20
|
+
git push -uf origin main
|
|
21
|
+
```
|
|
22
|
+
|
|
23
|
+
## Integrate with your tools
|
|
24
|
+
|
|
25
|
+
- [ ] [Set up project integrations](https://gitlab.com/vz-web/vz-common-translations/-/settings/integrations)
|
|
26
|
+
|
|
27
|
+
## Collaborate with your team
|
|
28
|
+
|
|
29
|
+
- [ ] [Invite team members and collaborators](https://docs.gitlab.com/ee/user/project/members/)
|
|
30
|
+
- [ ] [Create a new merge request](https://docs.gitlab.com/ee/user/project/merge_requests/creating_merge_requests.html)
|
|
31
|
+
- [ ] [Automatically close issues from merge requests](https://docs.gitlab.com/ee/user/project/issues/managing_issues.html#closing-issues-automatically)
|
|
32
|
+
- [ ] [Enable merge request approvals](https://docs.gitlab.com/ee/user/project/merge_requests/approvals/)
|
|
33
|
+
- [ ] [Set auto-merge](https://docs.gitlab.com/ee/user/project/merge_requests/merge_when_pipeline_succeeds.html)
|
|
34
|
+
|
|
35
|
+
## Test and Deploy
|
|
36
|
+
|
|
37
|
+
Use the built-in continuous integration in GitLab.
|
|
38
|
+
|
|
39
|
+
- [ ] [Get started with GitLab CI/CD](https://docs.gitlab.com/ee/ci/quick_start/index.html)
|
|
40
|
+
- [ ] [Analyze your code for known vulnerabilities with Static Application Security Testing (SAST)](https://docs.gitlab.com/ee/user/application_security/sast/)
|
|
41
|
+
- [ ] [Deploy to Kubernetes, Amazon EC2, or Amazon ECS using Auto Deploy](https://docs.gitlab.com/ee/topics/autodevops/requirements.html)
|
|
42
|
+
- [ ] [Use pull-based deployments for improved Kubernetes management](https://docs.gitlab.com/ee/user/clusters/agent/)
|
|
43
|
+
- [ ] [Set up protected environments](https://docs.gitlab.com/ee/ci/environments/protected_environments.html)
|
|
44
|
+
|
|
45
|
+
***
|
|
46
|
+
|
|
47
|
+
# Editing this README
|
|
48
|
+
|
|
49
|
+
When you're ready to make this README your own, just edit this file and use the handy template below (or feel free to structure it however you want - this is just a starting point!). Thanks to [makeareadme.com](https://www.makeareadme.com/) for this template.
|
|
50
|
+
|
|
51
|
+
## Suggestions for a good README
|
|
52
|
+
|
|
53
|
+
Every project is different, so consider which of these sections apply to yours. The sections used in the template are suggestions for most open source projects. Also keep in mind that while a README can be too long and detailed, too long is better than too short. If you think your README is too long, consider utilizing another form of documentation rather than cutting out information.
|
|
54
|
+
|
|
55
|
+
## Name
|
|
56
|
+
Choose a self-explaining name for your project.
|
|
57
|
+
|
|
58
|
+
## Description
|
|
59
|
+
Let people know what your project can do specifically. Provide context and add a link to any reference visitors might be unfamiliar with. A list of Features or a Background subsection can also be added here. If there are alternatives to your project, this is a good place to list differentiating factors.
|
|
60
|
+
|
|
61
|
+
## Badges
|
|
62
|
+
On some READMEs, you may see small images that convey metadata, such as whether or not all the tests are passing for the project. You can use Shields to add some to your README. Many services also have instructions for adding a badge.
|
|
63
|
+
|
|
64
|
+
## Visuals
|
|
65
|
+
Depending on what you are making, it can be a good idea to include screenshots or even a video (you'll frequently see GIFs rather than actual videos). Tools like ttygif can help, but check out Asciinema for a more sophisticated method.
|
|
66
|
+
|
|
67
|
+
## Installation
|
|
68
|
+
Within a particular ecosystem, there may be a common way of installing things, such as using Yarn, NuGet, or Homebrew. However, consider the possibility that whoever is reading your README is a novice and would like more guidance. Listing specific steps helps remove ambiguity and gets people to using your project as quickly as possible. If it only runs in a specific context like a particular programming language version or operating system or has dependencies that have to be installed manually, also add a Requirements subsection.
|
|
69
|
+
|
|
70
|
+
## Usage
|
|
71
|
+
Use examples liberally, and show the expected output if you can. It's helpful to have inline the smallest example of usage that you can demonstrate, while providing links to more sophisticated examples if they are too long to reasonably include in the README.
|
|
72
|
+
|
|
73
|
+
## Support
|
|
74
|
+
Tell people where they can go to for help. It can be any combination of an issue tracker, a chat room, an email address, etc.
|
|
75
|
+
|
|
76
|
+
## Roadmap
|
|
77
|
+
If you have ideas for releases in the future, it is a good idea to list them in the README.
|
|
78
|
+
|
|
79
|
+
## Contributing
|
|
80
|
+
State if you are open to contributions and what your requirements are for accepting them.
|
|
81
|
+
|
|
82
|
+
For people who want to make changes to your project, it's helpful to have some documentation on how to get started. Perhaps there is a script that they should run or some environment variables that they need to set. Make these steps explicit. These instructions could also be useful to your future self.
|
|
83
|
+
|
|
84
|
+
You can also document commands to lint the code or run tests. These steps help to ensure high code quality and reduce the likelihood that the changes inadvertently break something. Having instructions for running tests is especially helpful if it requires external setup, such as starting a Selenium server for testing in a browser.
|
|
85
|
+
|
|
86
|
+
## Authors and acknowledgment
|
|
87
|
+
Show your appreciation to those who have contributed to the project.
|
|
88
|
+
|
|
89
|
+
## License
|
|
90
|
+
For open source projects, say how it is licensed.
|
|
91
|
+
|
|
92
|
+
## Project status
|
|
93
|
+
If you have run out of energy or time for your project, put a note at the top of the README saying that development has slowed down or stopped completely. Someone may choose to fork your project or volunteer to step in as a maintainer or owner, allowing your project to keep going. You can also make an explicit request for maintainers.
|
|
@@ -1090,6 +1090,7 @@
|
|
|
1090
1090
|
"App.customers.createFirstCustomer.body": "Starten Sie mit der Digitalisierung noch heute und erstellen Sie Ihren ersten Gast.",
|
|
1091
1091
|
"App.customers.createFirstCustomer.createCustomer": "Gast erstellen",
|
|
1092
1092
|
"App.customers.createFirstCustomer.title": "Erstellen Sie Ihren ersten Gast",
|
|
1093
|
+
"App.customers.createNewCustomer": "Neuen kunden anlegen",
|
|
1093
1094
|
"App.customers.customer.addCustomer": "Gast hinzufügen",
|
|
1094
1095
|
"App.customers.customer.bookingHistory.link": "Link",
|
|
1095
1096
|
"App.customers.customer.bookingHistory.viewBooking": "Buchung anzeigen",
|
|
@@ -1627,7 +1628,7 @@
|
|
|
1627
1628
|
"App.whatsApp.support.link": "WhatsApp öffnen",
|
|
1628
1629
|
"App.whatsApp.support.subtitle": "QR-Code Scannen um den Chat mit Visitor auf Ihrem Handy zu öffnen",
|
|
1629
1630
|
"any.api.validation.INVALID_TYPE.locationDescription": "Ein unbekannter Fehler ist aufgetreten, bitte wenden sie sich an den Visitor Support",
|
|
1630
|
-
"any.api.validation.general.error": "Ein
|
|
1631
|
+
"any.api.validation.general.error": "Ein unerwarteter Fehler ist aufgetreten. Bitte versuchen Sie es erneut und wenn das Problem weiterhin besteht, kontaktieren Sie unser Support-Team.",
|
|
1631
1632
|
"backendApiClient.unknownError": "Ein unerwarteter Fehler ist aufgetreten. Unser Personal wurde benachrichtigt und arbeitet an einer Lösung.",
|
|
1632
1633
|
"main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Buchung kann nicht erstellt werden, da einige der Zimmer nicht mehr verfügbar sind",
|
|
1633
1634
|
"main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Kann nicht synchronisiert werden, da diese Buchung sich mit einer anderen im selben Zimmer überschneidet",
|
|
@@ -1090,6 +1090,7 @@
|
|
|
1090
1090
|
"App.customers.createFirstCustomer.body": "Start digitalizing your business today by adding your first customer.",
|
|
1091
1091
|
"App.customers.createFirstCustomer.createCustomer": "Create customer",
|
|
1092
1092
|
"App.customers.createFirstCustomer.title": "Create your first customer",
|
|
1093
|
+
"App.customers.createNewCustomer": "Create new customer",
|
|
1093
1094
|
"App.customers.customer.addCustomer": "Add customer",
|
|
1094
1095
|
"App.customers.customer.bookingHistory.link": "Link",
|
|
1095
1096
|
"App.customers.customer.bookingHistory.viewBooking": "View booking",
|
|
@@ -1627,7 +1628,7 @@
|
|
|
1627
1628
|
"App.whatsApp.support.link": "Open WhatsApp",
|
|
1628
1629
|
"App.whatsApp.support.subtitle": "Scan the QR code or click the button to go directly to the chat with Visitor.",
|
|
1629
1630
|
"any.api.validation.INVALID_TYPE.locationDescription": "An unexpected error has occured. Please contact Visitor support.",
|
|
1630
|
-
"any.api.validation.general.error": "An unexpected error has occured. Please contact
|
|
1631
|
+
"any.api.validation.general.error": "An unexpected error has occured. Please try again and if the issue persists contact our support team.",
|
|
1631
1632
|
"backendApiClient.unknownError": "An unexpected error has occurred. Our staff has been notified and is working on a fix.",
|
|
1632
1633
|
"main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Cannot create the booking because some of the rooms are no longer available",
|
|
1633
1634
|
"main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Cannot import the bookings because some of them overlap.",
|
|
@@ -1090,6 +1090,7 @@
|
|
|
1090
1090
|
"App.customers.createFirstCustomer.body": "Comience a digitalizar su negocio hoy mismo agregando su primer cliente.",
|
|
1091
1091
|
"App.customers.createFirstCustomer.createCustomer": "Crear cliente",
|
|
1092
1092
|
"App.customers.createFirstCustomer.title": "Crea tu primer cliente",
|
|
1093
|
+
"App.customers.createNewCustomer": "Crear nuevo cliente",
|
|
1093
1094
|
"App.customers.customer.addCustomer": "Agregar cliente",
|
|
1094
1095
|
"App.customers.customer.bookingHistory.link": "Enlace",
|
|
1095
1096
|
"App.customers.customer.bookingHistory.viewBooking": "Ver reserva",
|
|
@@ -1627,7 +1628,7 @@
|
|
|
1627
1628
|
"App.whatsApp.support.link": "Abre Wharsapp",
|
|
1628
1629
|
"App.whatsApp.support.subtitle": "Escanee el código QR o haga clic en el botón para ir directamente al chat con el Visitor.",
|
|
1629
1630
|
"any.api.validation.INVALID_TYPE.locationDescription": "Se ha producido un error inesperado. Póngase en contacto con el servicio de asistencia al Visitor.",
|
|
1630
|
-
"any.api.validation.general.error": "Se ha producido un error inesperado.
|
|
1631
|
+
"any.api.validation.general.error": "Se ha producido un error inesperado. Por favor, inténtelo de nuevo y si el problema persiste, póngase en contacto con nuestro equipo de soporte.",
|
|
1631
1632
|
"backendApiClient.unknownError": "Se ha producido un error inesperado. Nuestro equipo ha sido notificado y está trabajando en una solución.",
|
|
1632
1633
|
"main.api.bookings.cannotSync.noRoomAvailable.createBooking": "No se puede crear la reserva porque algunas de las habitaciones ya no están disponibles",
|
|
1633
1634
|
"main.api.bookings.cannotSync.noRoomAvailable.importBookings": "No se pueden importar las reservas porque algunas de ellas se superponen",
|
|
@@ -1090,6 +1090,7 @@
|
|
|
1090
1090
|
"App.customers.createFirstCustomer.body": "Commencez à numériser votre entreprise dès aujourd'hui en ajoutant votre premier client.",
|
|
1091
1091
|
"App.customers.createFirstCustomer.createCustomer": "Créer un client",
|
|
1092
1092
|
"App.customers.createFirstCustomer.title": "Créez votre premier client",
|
|
1093
|
+
"App.customers.createNewCustomer": "Créer un nouveau client",
|
|
1093
1094
|
"App.customers.customer.addCustomer": "Ajouter un client",
|
|
1094
1095
|
"App.customers.customer.bookingHistory.link": "Lien",
|
|
1095
1096
|
"App.customers.customer.bookingHistory.viewBooking": "Voir la réservation",
|
|
@@ -1627,7 +1628,7 @@
|
|
|
1627
1628
|
"App.whatsApp.support.link": "Ouvrir WhatsApp",
|
|
1628
1629
|
"App.whatsApp.support.subtitle": "Scannez le code QR ou cliquez sur le bouton pour accéder directement au chat avec le visiteur.",
|
|
1629
1630
|
"any.api.validation.INVALID_TYPE.locationDescription": "Une erreur inattendue s'est produite. Veuillez contacter l'assistance aux visiteurs.",
|
|
1630
|
-
"any.api.validation.general.error": "Une erreur inattendue
|
|
1631
|
+
"any.api.validation.general.error": "Une erreur inattendue est survenue. Veuillez réessayer et si le problème persiste, contactez notre équipe de support.",
|
|
1631
1632
|
"backendApiClient.unknownError": "Une erreur inattendue s'est produite. Notre équipe a été informée et travaille sur une solution.",
|
|
1632
1633
|
"main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Impossible de créer la réservation car certaines chambres ne sont plus disponibles",
|
|
1633
1634
|
"main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Impossible d'importer les réservations car certaines d'entre elles se chevauchent.",
|
|
@@ -1090,6 +1090,7 @@
|
|
|
1090
1090
|
"App.customers.createFirstCustomer.body": "Inizia a digitalizzare la tua attività oggi aggiungendo il tuo primo cliente.",
|
|
1091
1091
|
"App.customers.createFirstCustomer.createCustomer": "Crea cliente",
|
|
1092
1092
|
"App.customers.createFirstCustomer.title": "Crea il tuo primo cliente",
|
|
1093
|
+
"App.customers.createNewCustomer": "Crea nuovo cliente",
|
|
1093
1094
|
"App.customers.customer.addCustomer": "Aggiungi cliente",
|
|
1094
1095
|
"App.customers.customer.bookingHistory.link": "Link",
|
|
1095
1096
|
"App.customers.customer.bookingHistory.viewBooking": "Visualizza prenotazione",
|
|
@@ -1627,7 +1628,7 @@
|
|
|
1627
1628
|
"App.whatsApp.support.link": "Apri WhatsApp",
|
|
1628
1629
|
"App.whatsApp.support.subtitle": "Scansiona il codice QR o clicca il pulsante per andare direttamente alla chat con il Visitatore.",
|
|
1629
1630
|
"any.api.validation.INVALID_TYPE.locationDescription": "Si è verificato un errore imprevisto. Contatta l'assistenza per i visitatori.",
|
|
1630
|
-
"any.api.validation.general.error": "Si è verificato un errore imprevisto.
|
|
1631
|
+
"any.api.validation.general.error": "Si è verificato un errore imprevisto. Per favore riprova e se il problema persiste contatta il nostro team di supporto.",
|
|
1631
1632
|
"backendApiClient.unknownError": "Si è verificato un errore imprevisto. Il nostro personale è stato informato e sta lavorando per risolvere il problema.",
|
|
1632
1633
|
"main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Impossibile creare la prenotazione perché alcune camere non sono più disponibili",
|
|
1633
1634
|
"main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Impossibile importare le prenotazioni perché alcune di esse si sovrappongono.",
|
|
@@ -1090,6 +1090,7 @@
|
|
|
1090
1090
|
"App.customers.createFirstCustomer.body": "Începeți să digitalizați afacerea dvs. astăzi adăugând primul client.",
|
|
1091
1091
|
"App.customers.createFirstCustomer.createCustomer": "Creați client",
|
|
1092
1092
|
"App.customers.createFirstCustomer.title": "Creați primul dvs. client",
|
|
1093
|
+
"App.customers.createNewCustomer": "Adaugă client nou",
|
|
1093
1094
|
"App.customers.customer.addCustomer": "Adăugați client",
|
|
1094
1095
|
"App.customers.customer.bookingHistory.link": "Link",
|
|
1095
1096
|
"App.customers.customer.bookingHistory.viewBooking": "Vizualizare rezervare",
|
|
@@ -1627,7 +1628,7 @@
|
|
|
1627
1628
|
"App.whatsApp.support.link": "Deschideți WhatsApp",
|
|
1628
1629
|
"App.whatsApp.support.subtitle": "Scanați codul QR sau apăsați butonul pentru a merge direct la chat-ul cu vizitatorul.",
|
|
1629
1630
|
"any.api.validation.INVALID_TYPE.locationDescription": "A apărut o eroare neașteptată. Vă rugăm să contactați suportul Visitor.",
|
|
1630
|
-
"any.api.validation.general.error": "A apărut o eroare neașteptată. Vă rugăm să contactați
|
|
1631
|
+
"any.api.validation.general.error": "A apărut o eroare neașteptată. Vă rugăm să încercați din nou și, dacă problema persistă, contactați echipa noastră de asistență.",
|
|
1631
1632
|
"backendApiClient.unknownError": "A apărut o eroare neașteptată. Personalul nostru a fost notificat și lucrează la rezolvarea problemei.",
|
|
1632
1633
|
"main.api.bookings.cannotSync.noRoomAvailable.createBooking": "Nu se poate crea rezervarea pentru că unele dintre camere nu mai sunt disponibile",
|
|
1633
1634
|
"main.api.bookings.cannotSync.noRoomAvailable.importBookings": "Nu se pot importa rezervările pentru că unele dintre ele se suprapun.",
|
package/package.json
CHANGED
|
@@ -1,70 +1,70 @@
|
|
|
1
|
-
{
|
|
2
|
-
"name": "@hyper.software/visitor-common-translations",
|
|
3
|
-
"version": "2.0.
|
|
4
|
-
"author": "Hyper Software <tomescu.raul+hyper@gmail.com>",
|
|
5
|
-
"description": "Visitor Common Translations",
|
|
6
|
-
"main": "lib/index.js",
|
|
7
|
-
"types": "./lib/index.d.ts",
|
|
8
|
-
"engines": {
|
|
9
|
-
"node": ">= 18.18.0"
|
|
10
|
-
},
|
|
11
|
-
"files": [
|
|
12
|
-
"lib",
|
|
13
|
-
"es"
|
|
14
|
-
],
|
|
15
|
-
"keywords": [
|
|
16
|
-
"Javascript",
|
|
17
|
-
"translations"
|
|
18
|
-
],
|
|
19
|
-
"repository": {},
|
|
20
|
-
"license": "ISC",
|
|
21
|
-
"bugs": {},
|
|
22
|
-
"scripts": {
|
|
23
|
-
"test": "jest --watch --runInBand",
|
|
24
|
-
"test.coverage": "jest --coverage",
|
|
25
|
-
"lint": "eslint src --ext .ts,.tsx",
|
|
26
|
-
"format": "prettier-eslint \"src/**/*.ts\" \"src/**/*.tsx\" --write",
|
|
27
|
-
"build": "tsc",
|
|
28
|
-
"publish-package": "yarn translations-fix && git add . && git commit -m 'Pre-publish package' --allow-empty && rm -rf ./lib && yarn tsc && npm version patch && npm publish && git add . && git commit -m 'Post-publish package' --allow-empty && git push"
|
|
29
|
-
},
|
|
30
|
-
"husky": {
|
|
31
|
-
"hooks": {
|
|
32
|
-
"pre-commit": "tsc && npm run lint && npm run format"
|
|
33
|
-
}
|
|
34
|
-
},
|
|
35
|
-
"dependencies": {
|
|
36
|
-
"intl-format-cache": "^4.3.1",
|
|
37
|
-
"intl-messageformat": "^10.5.4",
|
|
38
|
-
"library-name": "^1.1.0"
|
|
39
|
-
},
|
|
40
|
-
"devDependencies": {
|
|
41
|
-
"@types/jest": "^29.5.7",
|
|
42
|
-
"@types/node": "^20.8.10",
|
|
43
|
-
"cross-env": "^7.0.3",
|
|
44
|
-
"er-translations-fix": "^1.0.7",
|
|
45
|
-
"identity-obj-proxy": "^3.0.0",
|
|
46
|
-
"in-publish": "^2.0.1",
|
|
47
|
-
"jest": "^29.7.0",
|
|
48
|
-
"prettier": "^3.0.3",
|
|
49
|
-
"rimraf": "^5.0.5",
|
|
50
|
-
"typescript": "^5.2.2"
|
|
51
|
-
},
|
|
52
|
-
"jest": {
|
|
53
|
-
"transform": {
|
|
54
|
-
".*": "<rootDir>/jest-preprocessor.js"
|
|
55
|
-
},
|
|
56
|
-
"testRegex": "(/__tests__/.*\\.(test|spec))\\.(ts|js)$",
|
|
57
|
-
"modulePaths": [
|
|
58
|
-
"./src"
|
|
59
|
-
],
|
|
60
|
-
"moduleFileExtensions": [
|
|
61
|
-
"js",
|
|
62
|
-
"json",
|
|
63
|
-
"ts"
|
|
64
|
-
],
|
|
65
|
-
"moduleDirectories": [
|
|
66
|
-
"node_modules",
|
|
67
|
-
"src"
|
|
68
|
-
]
|
|
69
|
-
}
|
|
70
|
-
}
|
|
1
|
+
{
|
|
2
|
+
"name": "@hyper.software/visitor-common-translations",
|
|
3
|
+
"version": "2.0.86",
|
|
4
|
+
"author": "Hyper Software <tomescu.raul+hyper@gmail.com>",
|
|
5
|
+
"description": "Visitor Common Translations",
|
|
6
|
+
"main": "lib/index.js",
|
|
7
|
+
"types": "./lib/index.d.ts",
|
|
8
|
+
"engines": {
|
|
9
|
+
"node": ">= 18.18.0"
|
|
10
|
+
},
|
|
11
|
+
"files": [
|
|
12
|
+
"lib",
|
|
13
|
+
"es"
|
|
14
|
+
],
|
|
15
|
+
"keywords": [
|
|
16
|
+
"Javascript",
|
|
17
|
+
"translations"
|
|
18
|
+
],
|
|
19
|
+
"repository": {},
|
|
20
|
+
"license": "ISC",
|
|
21
|
+
"bugs": {},
|
|
22
|
+
"scripts": {
|
|
23
|
+
"test": "jest --watch --runInBand",
|
|
24
|
+
"test.coverage": "jest --coverage",
|
|
25
|
+
"lint": "eslint src --ext .ts,.tsx",
|
|
26
|
+
"format": "prettier-eslint \"src/**/*.ts\" \"src/**/*.tsx\" --write",
|
|
27
|
+
"build": "tsc",
|
|
28
|
+
"publish-package": "yarn translations-fix && git add . && git commit -m 'Pre-publish package' --allow-empty && rm -rf ./lib && yarn tsc && npm version patch && npm publish && git add . && git commit -m 'Post-publish package' --allow-empty && git push"
|
|
29
|
+
},
|
|
30
|
+
"husky": {
|
|
31
|
+
"hooks": {
|
|
32
|
+
"pre-commit": "tsc && npm run lint && npm run format"
|
|
33
|
+
}
|
|
34
|
+
},
|
|
35
|
+
"dependencies": {
|
|
36
|
+
"intl-format-cache": "^4.3.1",
|
|
37
|
+
"intl-messageformat": "^10.5.4",
|
|
38
|
+
"library-name": "^1.1.0"
|
|
39
|
+
},
|
|
40
|
+
"devDependencies": {
|
|
41
|
+
"@types/jest": "^29.5.7",
|
|
42
|
+
"@types/node": "^20.8.10",
|
|
43
|
+
"cross-env": "^7.0.3",
|
|
44
|
+
"er-translations-fix": "^1.0.7",
|
|
45
|
+
"identity-obj-proxy": "^3.0.0",
|
|
46
|
+
"in-publish": "^2.0.1",
|
|
47
|
+
"jest": "^29.7.0",
|
|
48
|
+
"prettier": "^3.0.3",
|
|
49
|
+
"rimraf": "^5.0.5",
|
|
50
|
+
"typescript": "^5.2.2"
|
|
51
|
+
},
|
|
52
|
+
"jest": {
|
|
53
|
+
"transform": {
|
|
54
|
+
".*": "<rootDir>/jest-preprocessor.js"
|
|
55
|
+
},
|
|
56
|
+
"testRegex": "(/__tests__/.*\\.(test|spec))\\.(ts|js)$",
|
|
57
|
+
"modulePaths": [
|
|
58
|
+
"./src"
|
|
59
|
+
],
|
|
60
|
+
"moduleFileExtensions": [
|
|
61
|
+
"js",
|
|
62
|
+
"json",
|
|
63
|
+
"ts"
|
|
64
|
+
],
|
|
65
|
+
"moduleDirectories": [
|
|
66
|
+
"node_modules",
|
|
67
|
+
"src"
|
|
68
|
+
]
|
|
69
|
+
}
|
|
70
|
+
}
|