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
Jeff
Moderator
3 Questions, 2 Answers
  Active since 10 July 2023
  Last activity 4 months ago

Reputation

21 + 3 this April 0 4

Badges 3

Editor 2 × Eureka! Newbie
0 Votes
3 Answers
6K Views
0 Votes 3 Answers 6K Views
Standard method for defining opcodes in func?
Hello, I've been exploring different repositories and noticed inconsistencies in how opcodes are defined. For example, in the ft and nft implementation withi...
4 months ago
0 Votes
1 Answers
9K Views
0 Votes 1 Answers 9K Views
Inconsistent slice when calling my_address() in different contexts
I am encountering an inconsistency when calling my_address() in different contexts and hope someone can help me understand why this is happening. When I call...
6 months ago
0 Votes
2 Answers
13K Views
0 Votes 2 Answers 13K Views
Bitwise operation does not work as expected
I found a strange behavior in func bitwise operation. I don't understand why. slice slice0 = begin_cell().store_coins(123).end_cell().begin_parse(); int resu...
9 months ago
0 Standard method for defining opcodes in func?

Thank you for the clarification!

Also, I think the nft standard implementation should be updated. It currently uses builder_null?, which no longer exists in stdlib, and defines opcodes using the outdated method. This can be confusing, especially for newcomers to the language

4 months ago
0 Bitwise operation does not work as expected

Thanks!

9 months ago