@hyper.software/visitor-common-translations 2.0.155 → 2.0.157

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 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.
@@ -1 +1 @@
1
- {"version":3,"file":"TranslationsProvider.js","sourceRoot":"","sources":["../src/TranslationsProvider.ts"],"names":[],"mappings":";;;AAAA,yDAAmD;AACnD,uDAAuD;AACvD,yCAAuC;AAEvC;IAyCE,8BAAY,YAAsB;QAAtB,6BAAA,EAAA,iBAAsB;QAF1B,iBAAY,GAAQ,IAAI,CAAC;QAG/B,IAAI,CAAC,YAAY,GAAG,YAAY,CAAC;IACnC,CAAC;IA1Ca,mCAAc,GAAG,UAAC,QAA4C,EAAE,GAAW,EAAE,MAAgB;QAA3E,yBAAA,EAAA,WAA8B,oBAAQ,CAAC,KAAK;QAAe,uBAAA,EAAA,WAAgB;QACzG,IAAI,CAAC,oBAAoB,CAAC,kBAAkB,EAAE,EAAE;YAC9C,OAAO,IAAI,CAAC;SACb;QAED,IAAM,YAAY,GAAG,oBAAoB,CAAC,kBAAkB,EAAE,CAAC,YAAY,CAAC;QAE5E,IAAI,CAAC,QAAQ,IAAI,CAAC,YAAY,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,EAAE;YACtD,QAAQ,GAAG,oBAAQ,CAAC,KAAK,CAAC;SAC3B;QAED,IAAM,OAAO,GAAW,YAAY,IAAI,YAAY,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,IAAI,YAAY,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC;QAE1H,IAAI,CAAC,OAAO,EAAE;YACZ,OAAO,GAAG,CAAC;SACZ;QAED,IAAI;YACF,IAAM,SAAS,GAAG,oBAAoB,CAAC,gBAAgB,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;YAC3E,IAAM,gBAAgB,GAAG,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;YAClD,OAAO,gBAAgB,CAAC;SACzB;QAAC,OAAO,GAAG,EAAE;YACZ,+BAA+B;YAC/B,OAAO,OAAO,CAAC;SAChB;IACH,CAAC,AAzB2B,CAyB1B;IAEY,uCAAkB,GAAG;QACjC,OAAO,oBAAoB,CAAC,eAAe,CAAC;IAC9C,CAAC,AAF+B,CAE9B;IAEY,+BAAU,GAAG,UAAC,YAAsB;QAAtB,6BAAA,EAAA,iBAAsB;QAChD,oBAAoB,CAAC,gBAAgB,GAAG,IAAA,2BAAsB,EAAC,4BAAiB,CAAC,CAAC;QAClF,oBAAoB,CAAC,eAAe,GAAG,IAAI,oBAAoB,CAAC,YAAY,CAAC,CAAC;IAChF,CAAC,AAHuB,CAGtB;IAEa,qCAAgB,GAAG,IAAI,AAAP,CAAQ;IAOzC,2BAAC;CAAA,AA5CD,IA4CC;AA5CY,oDAAoB"}
1
+ {"version":3,"file":"TranslationsProvider.js","sourceRoot":"","sources":["../src/TranslationsProvider.ts"],"names":[],"mappings":";;;AAAA,yDAAmD;AACnD,uDAAuD;AACvD,yCAAuC;AAEvC;IAyCE,8BAAY,YAAsB;QAAtB,6BAAA,EAAA,iBAAsB;QAF1B,iBAAY,GAAQ,IAAI,CAAC;QAG/B,IAAI,CAAC,YAAY,GAAG,YAAY,CAAC;IACnC,CAAC;IA1Ca,mCAAc,GAAG,UAAC,QAA4C,EAAE,GAAW,EAAE,MAAgB;QAA3E,yBAAA,EAAA,WAA8B,oBAAQ,CAAC,KAAK;QAAe,uBAAA,EAAA,WAAgB;QACzG,IAAI,CAAC,oBAAoB,CAAC,kBAAkB,EAAE,EAAE,CAAC;YAC/C,OAAO,IAAI,CAAC;QACd,CAAC;QAED,IAAM,YAAY,GAAG,oBAAoB,CAAC,kBAAkB,EAAE,CAAC,YAAY,CAAC;QAE5E,IAAI,CAAC,QAAQ,IAAI,CAAC,YAAY,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,EAAE,CAAC;YACvD,QAAQ,GAAG,oBAAQ,CAAC,KAAK,CAAC;QAC5B,CAAC;QAED,IAAM,OAAO,GAAW,YAAY,IAAI,YAAY,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,IAAI,YAAY,CAAC,QAAQ,CAAC,WAAW,EAAE,CAAC,CAAC,GAAG,CAAC,CAAC;QAE1H,IAAI,CAAC,OAAO,EAAE,CAAC;YACb,OAAO,GAAG,CAAC;QACb,CAAC;QAED,IAAI,CAAC;YACH,IAAM,SAAS,GAAG,oBAAoB,CAAC,gBAAgB,CAAC,OAAO,EAAE,QAAQ,CAAC,CAAC;YAC3E,IAAM,gBAAgB,GAAG,SAAS,CAAC,MAAM,CAAC,MAAM,CAAC,CAAC;YAClD,OAAO,gBAAgB,CAAC;QAC1B,CAAC;QAAC,OAAO,GAAG,EAAE,CAAC;YACb,+BAA+B;YAC/B,OAAO,OAAO,CAAC;QACjB,CAAC;IACH,CAAC,AAzB2B,CAyB1B;IAEY,uCAAkB,GAAG;QACjC,OAAO,oBAAoB,CAAC,eAAe,CAAC;IAC9C,CAAC,AAF+B,CAE9B;IAEY,+BAAU,GAAG,UAAC,YAAsB;QAAtB,6BAAA,EAAA,iBAAsB;QAChD,oBAAoB,CAAC,gBAAgB,GAAG,IAAA,2BAAsB,EAAC,4BAAiB,CAAC,CAAC;QAClF,oBAAoB,CAAC,eAAe,GAAG,IAAI,oBAAoB,CAAC,YAAY,CAAC,CAAC;IAChF,CAAC,AAHuB,CAGtB;IAEa,qCAAgB,GAAG,IAAI,AAAP,CAAQ;IAOzC,2BAAC;CAAA,AA5CD,IA4CC;AA5CY,oDAAoB"}
@@ -290,6 +290,7 @@
290
290
  "App.bookings.bookingsTitle": "Buchungen",
291
291
  "App.bookings.cancelBooking.sendCancellationEmail": "Gast über die Stornierung per E-Mail informieren",
292
292
  "App.bookings.childrenRatesCost": "Kosten für Kinder:",
293
+ "App.bookings.common.room": "Zimmer",
293
294
  "App.bookings.createBooking.sendConfirmationEmail": "Gast die Buchung per E-Mail bestätigen",
294
295
  "App.bookings.createBooking.sendCreatedEmailToAdmin": "Sende \"Buchungsbestätigung per E-Mail\" an Administrator",
295
296
  "App.bookings.createBooking.success": "Buchung wurde erfolgreich erstellt",
@@ -307,6 +308,7 @@
307
308
  "App.bookings.details.checkIn.revert": "Check-in entfernen",
308
309
  "App.bookings.details.checkOut": "Check-out Datum",
309
310
  "App.bookings.details.checkedIn": "Checked in",
311
+ "App.bookings.details.children": "Kinder",
310
312
  "App.bookings.details.creationDate": "Erstelldatum",
311
313
  "App.bookings.details.delete.warning": "Sie im Begriff, eine Buchung zu stornieren, welche über ein OTAs (Online-Reisebüros) getätigt wurde. Aufgrund der Stornierungsrichtlinien muss eine Stornierungsanfrage hier direkt über den OTA gestellt werden. Nachdem Ihr Gast diese akzeptiert hat, wird sie automatisch aus Ihrem Belegungskalender herausgelöscht. Bei Fragen hierzu stehen wir Ihnen gerne zur Verfügung.",
312
314
  "App.bookings.details.guests": "Gäste",
@@ -835,7 +837,7 @@
835
837
  "App.common.login": "Login",
836
838
  "App.common.logo": "Hotel Logo",
837
839
  "App.common.menu.bookings": "Buchungen",
838
- "App.common.menu.bookingsImport": "Buchungen importieren",
840
+ "App.common.menu.bookingsImport": "Importieren das Buchungen",
839
841
  "App.common.menu.calendar": "Kalender",
840
842
  "App.common.menu.channels": "Channels",
841
843
  "App.common.menu.companies": "Unternehmen",
@@ -1132,6 +1134,9 @@
1132
1134
  "App.common.welcomeBack.noFirstName": "Willkommen zurück!",
1133
1135
  "App.common.welcomeBack.withFirstName": "Willkommen zurück, {firstName}!",
1134
1136
  "App.common.yes": "Ja",
1137
+ "App.companies.createCompany.title": "",
1138
+ "App.companies.editCompany.title": "",
1139
+ "App.company.name": "",
1135
1140
  "App.customer.customerDetails.bookings.backTitle": "Zurück zu den Buchungsdetails",
1136
1141
  "App.customer.details.additionalGuests": "Zusätzlicher Gast {guestNumber}",
1137
1142
  "App.customer.details.customerNotes": "Details",
@@ -290,6 +290,7 @@
290
290
  "App.bookings.bookingsTitle": "Bookings",
291
291
  "App.bookings.cancelBooking.sendCancellationEmail": "Send the cancellation email to the customer",
292
292
  "App.bookings.childrenRatesCost": "Cost for Children:",
293
+ "App.bookings.common.room": "Room",
293
294
  "App.bookings.createBooking.sendConfirmationEmail": "Send the confirmation email to the customer",
294
295
  "App.bookings.createBooking.sendCreatedEmailToAdmin": "Send the \"Booking was created email\" to the admin",
295
296
  "App.bookings.createBooking.success": "The booking was created successfully",
@@ -307,6 +308,7 @@
307
308
  "App.bookings.details.checkIn.revert": "Revert check-in",
308
309
  "App.bookings.details.checkOut": "Checkout date",
309
310
  "App.bookings.details.checkedIn": "Checked-in",
311
+ "App.bookings.details.children": "Children",
310
312
  "App.bookings.details.creationDate": "Creation date",
311
313
  "App.bookings.details.delete.warning": "You are trying to cancel a booking which was made through OTA’s. Due to their cancellation policy, a request cancellation has to be made through the OTA and the guest has to accept it. You can send us the name and date of the booking you wish to be cancelled and we will help you with it.",
312
314
  "App.bookings.details.guests": "Guests",
@@ -835,7 +837,7 @@
835
837
  "App.common.login": "Login",
836
838
  "App.common.logo": "Logo",
837
839
  "App.common.menu.bookings": "Bookings",
838
- "App.common.menu.bookingsImport": "Import Bookings",
840
+ "App.common.menu.bookingsImport": "Import",
839
841
  "App.common.menu.calendar": "Calendar",
840
842
  "App.common.menu.channels": "Channels",
841
843
  "App.common.menu.companies": "Companies",
@@ -1132,6 +1134,9 @@
1132
1134
  "App.common.welcomeBack.noFirstName": "Welcome back!",
1133
1135
  "App.common.welcomeBack.withFirstName": "Welcome back, {firstName}!",
1134
1136
  "App.common.yes": "Yes",
1137
+ "App.companies.createCompany.title": "Create Company",
1138
+ "App.companies.editCompany.title": "Edit Company",
1139
+ "App.company.name": "Company Name",
1135
1140
  "App.customer.customerDetails.bookings.backTitle": "Back to booking details",
1136
1141
  "App.customer.details.additionalGuests": "Additional Guest {guestNumber}",
1137
1142
  "App.customer.details.customerNotes": "Customer notes",
@@ -290,6 +290,7 @@
290
290
  "App.bookings.bookingsTitle": "Reservaciones",
291
291
  "App.bookings.cancelBooking.sendCancellationEmail": "Enviar el correo electrónico de cancelación al cliente",
292
292
  "App.bookings.childrenRatesCost": "Costo para niños:",
293
+ "App.bookings.common.room": "Habitación",
293
294
  "App.bookings.createBooking.sendConfirmationEmail": "Enviar el correo electrónico de confirmación al usuario",
294
295
  "App.bookings.createBooking.sendCreatedEmailToAdmin": "Enviar el correo electrónico de confirmación de la reserva al administrador",
295
296
  "App.bookings.createBooking.success": "Reserva se creó con éxito",
@@ -307,6 +308,7 @@
307
308
  "App.bookings.details.checkIn.revert": "Eliminar el check-in",
308
309
  "App.bookings.details.checkOut": "Fecha de salida",
309
310
  "App.bookings.details.checkedIn": "Registrado",
311
+ "App.bookings.details.children": "Niños",
310
312
  "App.bookings.details.creationDate": "Fecha de creación",
311
313
  "App.bookings.details.delete.warning": "",
312
314
  "App.bookings.details.guests": "Huéspedes",
@@ -1132,6 +1134,9 @@
1132
1134
  "App.common.welcomeBack.noFirstName": "¡Bienvenido de nuevo!",
1133
1135
  "App.common.welcomeBack.withFirstName": "¡Bienvenido de nuevo, {firstName}!",
1134
1136
  "App.common.yes": "Si",
1137
+ "App.companies.createCompany.title": "",
1138
+ "App.companies.editCompany.title": "",
1139
+ "App.company.name": "",
1135
1140
  "App.customer.customerDetails.bookings.backTitle": "Volver a los detalles de la reserva",
1136
1141
  "App.customer.details.additionalGuests": "Invitado adicional {guestNumber}",
1137
1142
  "App.customer.details.customerNotes": "Notas del cliente",
@@ -290,6 +290,7 @@
290
290
  "App.bookings.bookingsTitle": "Réservations",
291
291
  "App.bookings.cancelBooking.sendCancellationEmail": "Envoyer l'e-mail d'annulation au client",
292
292
  "App.bookings.childrenRatesCost": "Coût pour les enfants:",
293
+ "App.bookings.common.room": "Chambre",
293
294
  "App.bookings.createBooking.sendConfirmationEmail": "Envoyer l'e-mail de confirmation à l'utilisateur",
294
295
  "App.bookings.createBooking.sendCreatedEmailToAdmin": "Envoyer l'e-mail de confirmation de réservation à l'administrateur",
295
296
  "App.bookings.createBooking.success": "La réservation a été créée avec succès",
@@ -307,6 +308,7 @@
307
308
  "App.bookings.details.checkIn.revert": "Supprimer l'enregistrement",
308
309
  "App.bookings.details.checkOut": "Checkout date",
309
310
  "App.bookings.details.checkedIn": "Checked-in",
311
+ "App.bookings.details.children": "Enfants",
310
312
  "App.bookings.details.creationDate": "Date de création",
311
313
  "App.bookings.details.delete.warning": "",
312
314
  "App.bookings.details.guests": "Guests",
@@ -1132,6 +1134,9 @@
1132
1134
  "App.common.welcomeBack.noFirstName": "Bienvenue de retour!",
1133
1135
  "App.common.welcomeBack.withFirstName": "Bienvenue de retour, {firstName}!",
1134
1136
  "App.common.yes": "Oui",
1137
+ "App.companies.createCompany.title": "",
1138
+ "App.companies.editCompany.title": "",
1139
+ "App.company.name": "",
1135
1140
  "App.customer.customerDetails.bookings.backTitle": "Retour aux détails de la réservation",
1136
1141
  "App.customer.details.additionalGuests": "Invité supplémentaire {guestNumber}",
1137
1142
  "App.customer.details.customerNotes": "Notes du client",
@@ -290,6 +290,7 @@
290
290
  "App.bookings.bookingsTitle": "Prenotazioni",
291
291
  "App.bookings.cancelBooking.sendCancellationEmail": "Invia l'email di cancellazione al cliente",
292
292
  "App.bookings.childrenRatesCost": "Costo per bambini:",
293
+ "App.bookings.common.room": "Camera",
293
294
  "App.bookings.createBooking.sendConfirmationEmail": "Invia l'email di conferma all'utente",
294
295
  "App.bookings.createBooking.sendCreatedEmailToAdmin": "Invia l'email di conferma prenotazione all'amministratore",
295
296
  "App.bookings.createBooking.success": "La prenotazione è stata creata con successo",
@@ -307,6 +308,7 @@
307
308
  "App.bookings.details.checkIn.revert": "Rimuovi il check-in",
308
309
  "App.bookings.details.checkOut": "Data di checkout",
309
310
  "App.bookings.details.checkedIn": "Check-in",
311
+ "App.bookings.details.children": "Bambini",
310
312
  "App.bookings.details.creationDate": "Data di creazione",
311
313
  "App.bookings.details.delete.warning": "",
312
314
  "App.bookings.details.guests": "Ospiti",
@@ -1132,6 +1134,9 @@
1132
1134
  "App.common.welcomeBack.noFirstName": "Bentornato/a!",
1133
1135
  "App.common.welcomeBack.withFirstName": "Bentornato/a, {firstName}!",
1134
1136
  "App.common.yes": "Sì",
1137
+ "App.companies.createCompany.title": "",
1138
+ "App.companies.editCompany.title": "",
1139
+ "App.company.name": "",
1135
1140
  "App.customer.customerDetails.bookings.backTitle": "Torna ai dettagli della prenotazione",
1136
1141
  "App.customer.details.additionalGuests": "Ospite aggiuntivo {guestNumber}",
1137
1142
  "App.customer.details.customerNotes": "Note del cliente",
@@ -290,6 +290,7 @@
290
290
  "App.bookings.bookingsTitle": "Rezervări",
291
291
  "App.bookings.cancelBooking.sendCancellationEmail": "Trimiteți emailul de anulare către client",
292
292
  "App.bookings.childrenRatesCost": "Costul pentru copii:",
293
+ "App.bookings.common.room": "Camera",
293
294
  "App.bookings.createBooking.sendConfirmationEmail": "Trimite e-mailul de confirmare către utilizator",
294
295
  "App.bookings.createBooking.sendCreatedEmailToAdmin": "Trimite emailul de confirmare a rezervării către administrator",
295
296
  "App.bookings.createBooking.success": "Rezervarea a fost creată cu succes",
@@ -307,6 +308,7 @@
307
308
  "App.bookings.details.checkIn.revert": "Elimină check-in-ul",
308
309
  "App.bookings.details.checkOut": "Data de checkout",
309
310
  "App.bookings.details.checkedIn": "A făcut check-in",
311
+ "App.bookings.details.children": "Copii",
310
312
  "App.bookings.details.creationDate": "Data creării",
311
313
  "App.bookings.details.delete.warning": "",
312
314
  "App.bookings.details.guests": "Oaspeți",
@@ -1132,6 +1134,9 @@
1132
1134
  "App.common.welcomeBack.noFirstName": "Bine ai revenit!",
1133
1135
  "App.common.welcomeBack.withFirstName": "Bine ai revenit, {firstName}!",
1134
1136
  "App.common.yes": "Da",
1137
+ "App.companies.createCompany.title": "",
1138
+ "App.companies.editCompany.title": "",
1139
+ "App.company.name": "",
1135
1140
  "App.customer.customerDetails.bookings.backTitle": "Înapoi la detalii rezervare",
1136
1141
  "App.customer.details.additionalGuests": "Oaspete suplimentar {guestNumber}",
1137
1142
  "App.customer.details.customerNotes": "Note ale clientului",
package/package.json CHANGED
@@ -1,70 +1,70 @@
1
- {
2
- "name": "@hyper.software/visitor-common-translations",
3
- "version": "2.0.155",
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.157",
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
+ }