-
```
There are times when you want to apply a rule at morpheme or syllable
boundary, or where a rule should not apply across morph/syllable
boundaries. To support this, we should allow for boundary m…
-
There are a lot of use cases that aren't covered in the README. It would be nice to have a runnable "examples" folder that includes a bunch of common recipes.
-
**Describe the bug**
`Daytona server `works only on second try post install. Note my experience is after `Daytona Purge`
**To Reproduce**
Steps to reproduce the behavior:
1. Running Daytona do t…
-
Presently, algorithms must be captured as a single KiSAO term. This creates the need to create additional terms for each hybrid combination. A more flexible approach would be to allow inline descripti…
-
Redirect middleware is a very good idea, but it's usage is quite narrow. It would be good to use more generic approach, with richer exception hierarchy, which would allow to handle other response type…
cezio updated
11 years ago
-
```
This could include other kinds of error as well, but validation errors are
the most important, because they are the ones that may be exposed to the
least technical users.
Validation errors should…
-
### What is the expected behavior?
For generating richer query shape information, `QueryBuilder` implementations within OpenSearch plugins should implement (if relevant) recently introduced `WithFiel…
-
To power the CLI premium features we need to have insight into the features the platform has enabled.
The goal will be to use this to provide richer errors during CLI work and obscure features which…
-
Hi,
This paper was super interesting to read. I am working on a similar graph CO problem where my objective is to “activate” as many nodes as possible in the graph to maximize as many paths as poss…
-
Refs: #96927
It would be great to have some richer optional UI components that could be enabled within a custom view, e.g.
- [x] Search/Filter box
- [ ] General input box
- [ ] "Details" pane …