| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
| |
commit_hash:7579cfab3b598d951714e83b74e02d1d9b23cec2
|
|
|
|
| |
commit_hash:188eabb32fe62c00b28fbfd2ca438d751e66a540
|
|
|
|
| |
commit_hash:dc3193604b8e3f1c1a2e012318f542b2497d7638
|
|
|
|
|
| |
Update tools: test_tool, os_ya, ya_bin, os_test_tool
commit_hash:e1a9b4c4ac2cb1d4372a80cdaf9ff5ffad68f9f1
|
|
|
|
| |
commit_hash:e4127882c960fab8e539f5332c981e7adebc5cb5
|
|
|
|
| |
commit_hash:a97752fe47c21a472a780e6b2097cd7c20c63766
|
|
|
|
| |
commit_hash:66a9427951da5b22e74fc6c04f4a3b7fd8713510
|
|
|
|
| |
commit_hash:f557fe6f4960cb4466290d49e5f14af379ba2f94
|
|
|
|
| |
commit_hash:305fec3efc9087bab26ae2fca809e1c3c0723b00
|
|
|
|
|
| |
Remove semantics from EXTERNAL_JAVA_LIBRARY
commit_hash:30f823498fa04c4da5d137a99e1d24e15e7d5b93
|
|
|
|
| |
commit_hash:9b9fa862d523687c3eb883e9b94c2ecef522cda8
|
|
|
|
| |
commit_hash:065881aad5e9f774c9709037fdfd30b5d3c77d51
|
|
|
|
| |
commit_hash:2b01b1b2387f71903fc29f3364d1e5f46f35a703
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
When I tried to implement a folder and object names completion at `ID_QUOTED` I faced with a problem, that I actually can't detect, that cursor is at `ID_QUOTED` token because `TCompletionInput::Text` it was cut until the `TCompletionInput::CursorPosition`, therefore at input ``` SELECT * FROM `#` ``` prefix was ``` SELECT * FROM `# ``` and then lexer failed.
While we actually want tokenize the whole current statement, `C3` still needs to receive a prefix as input. I tried to tokenize the whole statement and then on input `SELECT Optional<#>` got nothing because `<>` is solid token in the `SQL`. The only way to fix it I found is to cut a query to prefix until the cursor position.
BTW, current implementation is not so efficient as we tokenize the input multiple times. Especially `SplitQueryToStatemnts` seems heavy. In future we anyway will parse the whole input so will need to design APIs to receive ready token streams to do statements splitting, for example, just not to do the work twice.

So I introduce you the following changes
- [x] Select the whole current statement, not just prefix.
- [x] Find the token at caret and output no candidates when caret is at `STRING_VALUE`, `DIGIGTS` and so on.
- [x] Change `C3` wrapper interface to take `TCompletionInput` to hide an implementation detail that it runs on cut prefix.
- [x] `#` annotated queries in unit tests.
- [x] Detect `CaretTokenPosition` -- if is it enclosed with a token or between two.
- [x] Ensure that `maxErrors` in `ILexer::Tokenize` is positive. Just a tiny bugfix.
---
- Related to https://github.com/ytsaurus/ytsaurus/pull/1209
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/14
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1225
commit_hash:a434b9888ec8a7356247d63d9f1420e256ae4fca
|
|
|
|
| |
commit_hash:f4f2e8b9ba31109593c94251f64e1061f00af304
|
|
|
|
| |
commit_hash:13b88581d861a38841bc1473ddb1ad07befea7ec
|
|
|
|
| |
commit_hash:09465895d52261f981de0dac35d5792dbf8d9b59
|
|
|
|
|
| |
https://github.com/yandex/toolchain-registry/releases/tag/clang18-v9
commit_hash:0c8b52ff29b719af33002f537095864d5c8e1aaf
|
|
|
|
| |
commit_hash:cc8e1d7c04d38c7d9f7d42a6f6f327c73ba11502
|
|
|
|
| |
commit_hash:5c78798b304a05a90b7e9a5b2bcdc1d3454d9f77
|
|
|
|
| |
commit_hash:4eeebcfb3a5a301157ffdf1f6fb562be65cc3011
|
|
|
|
| |
commit_hash:f6bb35748ba86b6c9a4a308231cf2ae10f1eeac7
|
|
|
|
| |
commit_hash:5117342b91cba57f7c45d262b1c95aea6a65061a
|
|
|
|
| |
commit_hash:df494d98a61d65d0b77b335f1e998670be2f9f2b
|
|
|
|
| |
commit_hash:ca0a881f294c00b673673335c9366699c4be7c86
|
|
|
|
| |
commit_hash:a1f6e10ba4e2df5b1e0a7e49410e245ed7b92ae3
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
I was lazy to search for a most frequent used name among equivalent by the relation `(a ~ b) iff (NormalizeName(a) = NormalizeName(b))`. Because it seems that names we receive from JSONs are canonized and therefore in a preferable style by the opinion of the YQL language designers. But because of duplicates at `statements_opensource.json` we have, for example, both `IGNORETYPEV3` and `IGNORE_TYPE_V3` in candidates list. I think that we should just remove `IGNORETYPEV3` from the JSON.
---
- Related to https://github.com/ydb-platform/ydb/issues/9056
- Related to https://github.com/vityaman/ydb/issues/21
---
Pull Request resolved: https://github.com/ytsaurus/ytsaurus/pull/1229
commit_hash:fe73374ae27df1fcacb0adccda930ec98ed1d7a6
|
|
|
|
| |
commit_hash:a1ac242ea5619c1e83dd638a82653e1d5c385821
|
|
|
|
| |
commit_hash:8996ef4edbac442c49c715386063883e7cb93ab5
|
|
|
|
| |
commit_hash:31b59370a1423bb42b78161908b85ef57b800e5c
|
|
|
|
| |
commit_hash:bc699799776c0e43669867c9ef261fb1e006efa4
|
|
|
|
| |
commit_hash:d92446f14c476da0a2e64664e0a97455e4d5d32a
|
|
|
|
| |
commit_hash:a4522facabf7d730438dfc794abddedb0838d79e
|
|
|
|
| |
commit_hash:1375a766562a6db3ebd530fb7a9eff5d458fbd53
|
|
|
|
| |
commit_hash:2af511a18740c931b471dc1f2ff36a8b4ce573a8
|
|
|
|
| |
commit_hash:50613d0577fc2473762b82ebce4337a7d399371d
|
|
|
|
| |
commit_hash:9accadbf8068e1d496f6fc9ea6b878476f55f89b
|
|
|
|
| |
commit_hash:3b48c6649d1d04e7bf7daf8f05835def10082f2a
|
|
|
|
| |
commit_hash:22ad01050569869e2e75f89e65b06abf113791e4
|
|
|
|
| |
commit_hash:112bf21627e2883a424e58d1a65caf7af62c24c8
|
|
|
|
|
| |
by @va-kuznecov
commit_hash:26d8159e9bd33f1dd9471154655b861b203dbe10
|
|
|
|
| |
commit_hash:9c2397eb157e2aa3eea3d19beafd5fbe7bb278d0
|
|
|
|
| |
commit_hash:d9a386a995ec4a3d300c1c1350fcfbe2028ddd35
|
|
|
|
|
|
| |
os_test_tool
commit_hash:dda60c054b8bb2116c8d85515903c81da4ec8162
|
|
|
|
| |
commit_hash:cb5d5094d0c0d7c7e07bed78fed7c15e9a0c1a29
|
|
|
|
|
| |
Update tools: test_tool, ya_bin, os_ya, os_test_tool
commit_hash:3fd9660023e4ca20fc278d88327288194d1841da
|
|
|
|
| |
commit_hash:5b013b23327d8b623fbe133c80d2188f62b421a6
|
|
|
|
| |
commit_hash:bdfb86ce1915fd5c298250f4973acf6343a3e226
|
|
|
|
| |
commit_hash:6e3f5fac6a8598586987b52d749644d1ce1fccbe
|
|
|
|
| |
commit_hash:478736ce9fbf76b0b269d4ac39055a3989b92e7f
|