`caretModel.caretsAndSelections = caretModel.caretsAndSelections` actually changes the position of the caret inside the selection. Then Fleet removes the selection, which leaves the caret in a random position.
GitOrigin-RevId: 0f0073b0bc191ac27fdef1b1fabb012a54700c23
It is not the responsibility of PsiWalker, but of JsonValueAdapter. No need for implementers to re-implement that logic
GitOrigin-RevId: 57ffc13818f0061a8055668be5163519f1b8eaae
The current alphabetic ordering was annoying to use, and it didn't actually assert anything the user could see anyways.
GitOrigin-RevId: e5e95c5877e85a6f3fe05cd1ec26094734ef9dde
It makes what you read in the tests closer to what the user experiences. Additionally, it also asserts the rendered behavior.
GitOrigin-RevId: e15be753a157945c988246db7bd3bd4473ce970c
New changes will add logic for `{ "not": { "required": [ "name" ] } }`, which would sound too ambiguous with currently existing "notRequired" logic.
GitOrigin-RevId: 70a6fc5f9ae44798ceb7c5b97a5f270436c80310
We don't want external plugins to rely on nested completions before the API has been finalized
GitOrigin-RevId: 2f9d0a4e26fabad35e909a3dbba618b19d8cc383
Ideally this is solved in formatter. But fixing formatter (IDEA-331479) is a much more complicated fix to debug into.
I've added a test that will detect when someone fixes the formatter, then they can revert this commit.
GitOrigin-RevId: d70ec5cfca675a84e2b1d5b915ca07b4ae7dea92
- Made intention preview available
- Merged subsequent read actions
- Made isAvailable work very fast
- Tried to set the same id to all commands to achieve single redo for the entire request, but that didn't work out yet
GitOrigin-RevId: 54f4a3458bb05d1a03729483a95b269fbf2875e0
Consider support of examples field as well, since they are both valid in the latest schema version
GitOrigin-RevId: cd65bc3c3bd19334fbf6ea42e545a8a349e9f236
Now, PCE is allowed to be cached. When PCE is fetched from the cache, it is ignored and the json schema is re-computed recursively (the recursion shouldn't happen more than once).
Thanks to Nicolay Mitropolsky for the idea!
GitOrigin-RevId: f662a8078396ee27c451d31c5297544a6d78a39d
The intention
- works with JSON schema
- reuses already existing syntax adapters
- inserts all known properties except those starting with $ sign (reference, schema, etc.)
GitOrigin-RevId: 2cbbae6e301436c9dfc1f5f53fab6b1fb59768e8
It inserts all known properties from the corresponding JSON-schema into the JsonObject a caret is located in.
GitOrigin-RevId: a48ef273a059283d6fa34ad25f7c06f30e77798c
Extract getDynamicSchema method to the service interface and change visibility modifier of the SchemaChecker to use them later in a dependent plugin
GitOrigin-RevId: a416fe20f3d5e7a2eca5c808b13b4061a8955f07
To avoid having an entire file highlighted, we explicitly narrow the erroneous text range to the first child's one -> UX does not suffer much
GitOrigin-RevId: ef6b849fa1e57d26166415924f583ff6d4269c09
