Replies: 2 comments
-
Sorry for the ambigours code above, the template argument export function registerEncodingHandlerFactory( arg: RegisterEncodingHandlerArg )
export interface RegisterEncodingHandlerArg {
encoding: string // The name of the encoding
makeHandler(schema: Uint8Array): ((message: MessageEvent<Uint8Array>) => MessageEvent<unknown>)
} I have no idea if it is possible and proper to expose an interface like this. If I made any mistake, I apologize for that. |
Beta Was this translation helpful? Give feedback.
0 replies
-
This feature is no longer needed, we should turn to the serialization frameworks which are well known. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Hi awesome foxglove team, would you please add support for custom message encoding via the API of extension authoring ?
There's a custom encoding called
portable
is in use among our system. We'd like to keep it simple to use the same MCAP file for both injecting and visualizing.The
portable
encoding supports dynamically data access via binary schema who carraies the reflecting information.We were expecting an interface for us to register one or more handler for messages transported using our custom encoding. Like this:
Thank you for your time.
Beta Was this translation helpful? Give feedback.
All reactions