In order to figure out if certain symbol is a future or not, HTML5 charts use the following method from the API: util.ParseSymbolType(symbol)

When I pass ESZ2660C to the method, I get back nothing. This in turn means that chart cannot figure out how to parse historical data, because it does not know how many fields to expect (which it deduces based on the symbol type).

We end up with empty charts for completely valid symbols.

Related issue, coming from Webstation team

Users started reporting weird formatting of prices in the HTML5 chart product for some symbols (yet everything worked fine for most of the other symbols).

The issue with more context demonstrating the problem is this one.

The actual problem is that for the symbol in question GMM.AX I'm not getting anything back when I call getProfile. This reproduces with the latest (at this moment) version of the API which is 3.0.3.

If this helps, when I change the symbol from TWTR to GMM.AX the following gets traced to the console:

GO GMM.AX=s
Connection.js:516:5
STOP TWTR=Ssc
Connection.js:516:5

I suspect letters behind = indicate what to do - more the better? - so while for Twitter there is Ssc for the problematic symbol we get only s (hope this helps).

@mvberg @bryaningl3 Could you please add index.d.ts file to the root folder?

declare module "@barchart/marketdata-api-js" {
    type EventType = 'events' | 'marketDepth' | 'marketUpdate' | 'cumulativeVolume' | 'timestamp' | string;

    type MarketDataCallback = (data: any) => void;

    class ConnectionBase {
        connect(server: string, username: string, password: string): void;
        disconnect(): void;
        pause(): void;
        resume(): void;
        on(eventType: EventType, callback: MarketDataCallback, symbol?: string): void;
        off(eventType: EventType, callback: MarketDataCallback, symbol?: string): void;
        getActiveSymbolCount(): any;
        getPollingFrequency(): number | null;
        setPollingFrequency(pollingFrequency: number | null): void;
        getMarketState(): MarketState;
        getServer(): string | null;
        getPassword(): string | null;
        getUsername(): string | null;
        toString(): string;
    }

    class Connection extends ConnectionBase {
        toString(): string;
    }

    class MarketState {
        constructor(handleProfileRequest?: (symbol: string) => void);
        getBook(symbol: string): any;
        getCumulativeVolume(symbol: string, callback: Function): Promise<any>;
        getProfile(symbol: string, callback: Function): Promise<any>;
        getQuote(symbol: string): any;
        getTimestamp(): Date;
    }

    const Util: any;
    const util: any;

    const MessageParser: any;
    const messageParser: any;

    const version: string;

    export {
        Connection,
        MarketState,
        Util,
        util,
        MessageParser,
        messageParser,
        version
    }
}

Without this file, I can't compile @barchart/demo-chart. And it will also add Intellisense for other repositories, that use this library.

Out of the box example for node.js does not seem to work.

For the case where the library is used/hosted in the server not managed by Barchart, we should not use the (hardcoded) relative URL proxies/instruments to fetch data. The base URL should be configurable.

Please see related discussion here.

Note that the setting has been added to the chart component, though it's not used there. We might opt to configure it only there and just pass it on to the API, or to configure the API separately.

@bryaningl3 let me know what you think.