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
53 lines
1.9 KiB
Objective-C
53 lines
1.9 KiB
Objective-C
/*
|
|
* Copyright (c) Meta Platforms, Inc. and affiliates.
|
|
*
|
|
* This source code is licensed under the MIT license found in the
|
|
* LICENSE file in the root directory of this source tree.
|
|
*/
|
|
|
|
#import <React/RCTBridgeModule.h>
|
|
#import <React/RCTURLRequestDelegate.h>
|
|
|
|
/**
|
|
* Provides the interface needed to register a request handler. Request handlers
|
|
* are also bridge modules, so should be registered using RCT_EXPORT_MODULE().
|
|
*/
|
|
@protocol RCTURLRequestHandler <RCTBridgeModule>
|
|
|
|
/**
|
|
* Indicates whether this handler is capable of processing the specified
|
|
* request. Typically the handler would examine the scheme/protocol of the
|
|
* request URL (and possibly the HTTP method and/or headers) to determine this.
|
|
*/
|
|
- (BOOL)canHandleRequest:(NSURLRequest *)request;
|
|
|
|
/**
|
|
* Send a network request and call the delegate with the response data. The
|
|
* method should return a token, which can be anything, including the request
|
|
* itself. This will be used later to refer to the request in callbacks. The
|
|
* `sendRequest:withDelegate:` method *must* return before calling any of the
|
|
* delegate methods, or the delegate won't recognize the token.
|
|
* Following common Objective-C pattern, `delegate` will not be retained.
|
|
*/
|
|
- (id)sendRequest:(NSURLRequest *)request withDelegate:(id<RCTURLRequestDelegate>)delegate;
|
|
|
|
@optional
|
|
|
|
/**
|
|
* Not all request types can be cancelled, but this method can be implemented
|
|
* for ones that can. It should be used to free up any resources on ongoing
|
|
* processes associated with the request.
|
|
*/
|
|
- (void)cancelRequest:(id)requestToken;
|
|
|
|
/**
|
|
* If more than one RCTURLRequestHandler responds YES to `canHandleRequest:`
|
|
* then `handlerPriority` is used to determine which one to use. The handler
|
|
* with the highest priority will be selected. Default priority is zero. If
|
|
* two or more valid handlers have the same priority, the selection order is
|
|
* undefined.
|
|
*/
|
|
- (float)handlerPriority;
|
|
|
|
@end
|