LinkinStars
LinkinStars
> anyone interested in taking this up can refer this piece of code: > > https://github.com/shreemaan-abhishek/apisix/blob/1f775c8ace851a8b8862801ad35e7cf4cd00851f/apisix/schema_def.lua#L739 > > This is exactly where the bug is. @shreemaan-abhishek This looks easier to...
> also, please fix the code lint problem I think it's probably not a code issue that's causing the lint to not pass. FYI: https://github.com/orgs/community/discussions/120966
@shreemaan-abhishek First, we discuss the issue of `env`. After my testing, **both the uppercase and lowercase should be supported** after changes. There are two reasons for this 1. unit test...
It looks like it's caused by `mockgen` not having to be installed successfully. Try using the `make generate` command to install it. Alternatively, you can use `go install github.com/golang/mock/[email protected]`
Firstly, thank you for your contribution. There are a few questions below: 1. Could you tell us some test cases for Persian to help us reproduce the problem? 2. If...
> @LinkinStars Thank you for response. I solved 3 and 4. > > 1. A post with this title has many redirect problem. > `title= چگونه میتوانم مساله گزارش شده...
https://github.com/apache/incubator-answer/blob/9681c026adfe4ddd0c8ae158b2f95e76e414df9f/pkg/htmltext/htmltext.go#L94 Our final solution is to use a fixed description(topic) when the language cannot be parsed.
In the new version, the search results will be uniformly formatted, filtering out markdown and html tags. Only normal text will be displayed here, not code or images.
Fixed in version [v0.4.0](https://github.com/answerdev/answer/releases/tag/v0.4.0).
Thanks for the feedback, we are checking the problem.