| name | description |
|---|---|
mapbox-search-patterns |
Expert guidance on choosing the right Mapbox search tool and parameters for geocoding, POI search, and location discovery |
Expert guidance for AI assistants on using Mapbox search tools effectively. Covers tool selection, parameter optimization, and best practices for geocoding, POI search, and location discovery.
| name | description |
|---|---|
mapbox-geospatial-operations |
Expert guidance on choosing the right geospatial tool based on problem type, accuracy requirements, and performance needs |
Expert guidance for AI assistants on choosing the right geospatial tools from the Mapbox MCP Server. Focuses on selecting tools based on what the problem requires - geometric calculations vs routing, straight-line vs road network, and accuracy needs.
This document explains the relationship between MCP Prompts and Agent Skills in the Mapbox MCP DevKit Server.
Prompts provide step-by-step workflows (orchestration) Skills provide domain expertise (knowledge) Tools provide capabilities (actions)
This document explains the relationship between MCP Prompts and Agent Skills in the Mapbox MCP DevKit Server.
Prompts provide step-by-step workflows (orchestration) Skills provide domain expertise (knowledge) Tools provide capabilities (actions)
I know there is a lot of confusion around Observables, Iterables, AsyncIterables and AsyncObservables. Let's try to break this down and the reasons for each.
When it comes to collections, you have two ways of thinking about collections, push versus pull. With pull, the consumer is in control of when you get the items, but with push, you get the values when the producer is ready.
| <Project Sdk="MSBuild.Sdk.Extras/2.0.54"> | |
| <PropertyGroup> | |
| <OutputType>Library</OutputType> | |
| <RootNamespace>Microsoft.Azure.NotificationHubs.Client</RootNamespace> | |
| <AssemblyName>Microsoft.Azure.NotificationHubs.Client</AssemblyName> | |
| <!-- Target both iOS and Android --> | |
| <TargetFrameworks>Xamarin.iOS10;MonoAndroid80;netstandard2.0</TargetFrameworks> | |
| <Product>$(AssemblyName) ($(TargetFramework))</Product> |
| using Foundation; | |
| using WindowsAzure.Messaging.NotificationHubs; | |
| namespace Microsoft.Azure.NotificationHubs | |
| { | |
| public partial class NotificationHub | |
| { | |
| private static readonly NotificationHubMessageDelegate _notificationHubMessageDelegate; | |
| static NotificationHub() |
The Interactive Extensions for JavaScript (IxJS) is a set of methods on top of Iteratable and AsyncIterable serving as a standard library for both. Much like its push-based counterpart, the Interactive Extensions for JavaScript unifies the programming model around pull-based collections, either synchronous in the case of Iterable or asynchronous with AsyncIterable.
Starting in ES6, the Symbol.iterator method was introduced to allow for iteration over collections such as Array, Map, Set and even ``Generator. IxJS introduces a number of creation factories and operators that operate on these Iterable` collections lazily. Each factory can be imported from `'ix/iterable'` and operators from `'ix/iterable/operators'` such as the following creating an iterable via `of` and then transforming each item using the `map` operator. You c
| #import <Foundation/Foundation.h> | |
| @class MSNotificationHub; | |
| @class MSInstallation; | |
| @protocol MSInstallationEnrichmentDelegate <NSObject> | |
| @optional | |
| - (void)notificationHub:(MSNotificationHub *)notificationHub willEnrichInstallation:(MSInstallation *)installation; |
| import { AsyncIterableX } from '../asynciterablex'; | |
| import { OperatorAsyncFunction } from '../../interfaces'; | |
| import { wrapWithAbort } from './withabort'; | |
| import { throwIfAborted } from '../../aborterror'; | |
| import { identity } from '../../util/identity'; | |
| // eslint-disable-next-line @typescript-eslint/no-empty-function | |
| const NEVER_PROMISE = new Promise(() => {}); | |
| type MergeResult<T> = { value: T; index: number }; |