marcogll/passkit-generator
1
0
Fork 0
mirror of https://github.com/marcogll/passkit-generator.git synced 2026-03-15 16:25:21 +00:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #72 from KristofKekesi/patch-1

Browse Source 
Improved non-mac-os-steps.md and API.md with typos fix
This commit is contained in:
Alexander Cerutti
2021-05-30 23:40:43 +02:00
committed by GitHub
parent e1c46491d6 593f1ce938
commit d9e4ef7dba
2 changed files with 5 additions and 5 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
API.md
View File

@@ -1,6 +1,6 @@
# API Reference
The flow of execution is really easy (once setted-up everything):
The flow of execution is really easy (once everything is set up):
* You get your data from somewhere
* You set the needed data in the pass through methods, overrides and data in fields
@@ -13,7 +13,7 @@ Some details:
* In case of troubleshooting, you can refer to the [Self-help](https://github.com/alexandercerutti/passkit-generator/wiki/Self-help) guide in Wiki or open an issue.
* Keep this as always valid for the reference:
* Keep this as it is always valid for the reference:
```javascript
const { createPass } = require("passkit-generator");
@@ -95,7 +95,7 @@ ___
Following Apple Developer Documentation, localization (L10N) is done by creating a `.lproj` folder for each language you want to translate your pass, each named with the relative [ISO-3166-1 alpha-2](https://it.wikipedia.org/wiki/ISO_3166-1_alpha-2) code (e.g. `en.lproj`).
In this library, localization can be done in three ways: **media-only** (images), **translations-only** or both.
The only differences stands in the way the only method below is used and how the model is designed.
The only difference stands in the way the only method below is used and how the model is designed.
If this method is used for translations and the model already contains a `pass.strings` for the specified language, the translations will be appended to that file.
> If you are designing your pass for a language only, you can directly replace the placeholders in `pass.json` with translation.
@@ -115,7 +115,7 @@ pass.localize(lang: string, options = {});
**Description**:
You may want to create the folder and add translated media and no translations; else you may want to add only translations without different medias or maybe both.
You may want to create the folder and add translated media with no translations; else you may want to add only translations without different media or maybe both.
In the first case, create the `.lproj` folder in the model root folder and add the translated medias inside. Then use the method by passing only the first parameters, the code.

2
non-macOS-steps.md
View File

@@ -3,7 +3,7 @@
This is a branch file that starts from the [Certificate paragraph](./README.md#certificates) and is made for developers that does not have access to macOS or are very very enthusiast of terminal (so its still valid for macOS).
I have to use these steps to work under WSL (Windows Subsystem for Linux), or Bash on Windows. The only thing you'll still need over the certificates, are an Wallet-ready iOS App (and so an iPhone) or a way to pass it.
To test it, I use my [Passkit-sample-client](https://github.com/alexandercerutti/passkit-sample-client), an really basic iOS App which requires just few informations and will show you the generated pass. Or you can use like Telegram, save your generated pass in your "Saved Messages" and then open it from the iPhone. Your choice.
To test it, I use my [Passkit-sample-client](https://github.com/alexandercerutti/passkit-sample-client), a really basic iOS App which requires just few informations and will show you the generated pass. Or you can use like Telegram, save your generated pass in your "Saved Messages" and then open it from the iPhone. Your choice.
But let's not talk anymore about testing and let's go with the steps to follow. **It will still require OpenSSL installed**. We are going to use it in a massive way.