e30ae8ed09
- App.tsx: full navigation (Auth stack + Main tabs with 5 screens) - Auth: LoginScreen, RegisterScreen, ForgotPasswordScreen - HomeScreen: dashboard with IoT metrics, weather widget, alerts, quick actions, sensors - MapScreen: interactive map with layer toggles (6 layers) - MarketplaceScreen: categories (6), products (5), search - ChatScreen: AI chat with quick prompts (4), bot responses - ProfileScreen: user info, stats, menu (9 items), logout - AlertsScreen: alert list with severity, acknowledge - SensorsScreen: sensor list with type filters (6 types), search - ZonesScreen: zone cards with stats - SettingsScreen: language picker (FR/EN/ES/DE), privacy, about - Stores: iotStore (sensors, zones, alerts), notificationStore, uiStore + i18n - Hooks: useSensors, useAlerts, useNotifications, useLocation - Components: Card, Button, LoadingSpinner, ErrorBoundary, Header - Services: iotService, notificationService (with axios API client) - Utils: formatters (temp, AQI, noise, dates), validators (email, password, IBAN) - Theme: colors.ts with full design system (Blue Ocean palette) - Ditto: fixed MongoDB connection, new JWT secrets, official gateway image
59 lines
1.3 KiB
Markdown
59 lines
1.3 KiB
Markdown
# p-try [](https://travis-ci.org/sindresorhus/p-try)
|
|
|
|
> Start a promise chain
|
|
|
|
[How is it useful?](http://cryto.net/~joepie91/blog/2016/05/11/what-is-promise-try-and-why-does-it-matter/)
|
|
|
|
|
|
## Install
|
|
|
|
```
|
|
$ npm install p-try
|
|
```
|
|
|
|
|
|
## Usage
|
|
|
|
```js
|
|
const pTry = require('p-try');
|
|
|
|
(async () => {
|
|
try {
|
|
const value = await pTry(() => {
|
|
return synchronousFunctionThatMightThrow();
|
|
});
|
|
console.log(value);
|
|
} catch (error) {
|
|
console.error(error);
|
|
}
|
|
})();
|
|
```
|
|
|
|
|
|
## API
|
|
|
|
### pTry(fn, ...arguments)
|
|
|
|
Returns a `Promise` resolved with the value of calling `fn(...arguments)`. If the function throws an error, the returned `Promise` will be rejected with that error.
|
|
|
|
Support for passing arguments on to the `fn` is provided in order to be able to avoid creating unnecessary closures. You probably don't need this optimization unless you're pushing a *lot* of functions.
|
|
|
|
#### fn
|
|
|
|
The function to run to start the promise chain.
|
|
|
|
#### arguments
|
|
|
|
Arguments to pass to `fn`.
|
|
|
|
|
|
## Related
|
|
|
|
- [p-finally](https://github.com/sindresorhus/p-finally) - `Promise#finally()` ponyfill - Invoked when the promise is settled regardless of outcome
|
|
- [More…](https://github.com/sindresorhus/promise-fun)
|
|
|
|
|
|
## License
|
|
|
|
MIT © [Sindre Sorhus](https://sindresorhus.com)
|