Examples: query, "exact match", wildcard*, wild?ard, wild*rd
Fuzzy search: cake~ (finds cakes, bake)
Term boost: "red velvet"^4, chocolate^2
Field grouping: tags:(+work -"fun-stuff")
Escape special characters +-&|!(){}[]^"~*?:\ - e.g. \+ \* \!
Range search: properties.timestamp:[1587729413488 TO *] (inclusive), properties.title:{A TO Z}(excluding A and Z)
Combinations: chocolate AND vanilla, chocolate OR vanilla, (chocolate OR vanilla) NOT "vanilla pudding"
Field search: properties.title:"The Title" AND text
 
Profile picture
Christopher H
Moderator
1 Question, 2 Answers
Active since 21 June 2023
  Last activity 2 months ago

Reputation

30 + 5 this October
0 Votes
1 Answers
99 Views
0 Votes 1 Answers 99 Views
Is the showOverpanel function intended to only open overpanels for the extension that calls it? We have an exposed entrypoint and overpanel configured on one...
11 months ago
0 LLM friendly Caliper documentation

As mentioned, the MCP server is probably the best option. If you need something that works offline, you can download the SDK from GitLab. The repository includes the full documentation, which can then be provided as context for the SDK when working with AI tools.

4 months ago
1 What are the use cases for user property data as opposed to user data?

user_data: quick per-user key/value storage. Best for lightweight, user-specific preferences or details you just want to keep track of.

user_property_data: a richer property system. Values are tied to elements and categories, making them suitable for feature flags, group-level settings, or other configurable attributes that need metadata (type, visibility rules, etc.).

In short:

Use user_data for tracking simple, per-user preferences (e.g., “prefers dark mode”).

Use user_property_...

one year ago