Skip to content
#

realtime

Here are 2,082 public repositories matching this topic...

markfields
markfields commented Oct 11, 2021

Looks like all the messages passed to throwBufferParseException are hardcoded and should be converted to error codes (camel case) and passed to createOdspNetworkError as the fluidErrorCode. Or, we could decide it's better to keep all these under one error code and leave it as-is, and close this.

_Originally posted by @markfields in microsoft/FluidFramework#7788

sharadregoti
sharadregoti commented Dec 18, 2020

The problem faced currently?

While adding an ingress route, or a target in ingress route.
If by mistake white space gets added to the route or host. We get the error specified route not found or unable to reach the specified target

How can we solve it?

Mission control should remove the white space if present before saving the config

If you want this feature to be implemented, gi

sanity
alevroub
alevroub commented Jun 26, 2018

The default google-maps-input.json could maybe include more displaying options, such as themes and zoom level for the static map. Though hacky, these few changes do the job for me:

GeopointSelect.js

var _googleMapsInput = require('config:@sanity/google-maps-input');
var _googleMapsInput2 = _interopRequireDefault(_googleMapsInput);

class GeopointSelect extends _react2.default.Compone
redpanda

Improve this page

Add a description, image, and links to the realtime topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the realtime topic, visit your repo's landing page and select "manage topics."

Learn more