qigao / durex Goto Github PK

set env vars from dotEnv for test task is not working

add logback config to all the webprojects

I as a developer, want to use a public jooq config for both reactive and imperative programming
when a public config is provided
then any repo like crud ops will use this with proper config

I as a system designer, wanna check potential bugs without ide or sonar
given the gradle building system
when running check
then it will print potential bug before submitting code

I as a system designer, wanna leverage redis in future development
then some redis examples should be introduced

scenario 1: redis service
scenario 2: redis example for web app

• create an annotation, such as validation
• validation it by json schema definition like hibernate validation
  json schema validator

I as a developer
when updating db config, i want a separate db config file
then i can use it as usual

introduce CSV Jackson

sonar CI needs a PR ID while merge to master only has a event ID,
using current PR will make merge check fail

processing large json/csv file should be carefully as it will needs lots of mem and time,

• generating large json (10k,100k,1000k,10M)
• Ser/De
• add unit test
• benchmarking(jmh?)

look into the json string below, we only need the text part

{
	"widget": {
		"debug": "on",
		"window": {
			"title": "Sample Konfabulator Widget",
			"name": "main_window",
			"width": 500,
			"height": 500
		},
		"image": {
			"src": "Images/Sun.png",
			"name": "sun1",
			"hOffset": 250,
			"vOffset": 250,
			"alignment": "center"
		},
		"text": {
			"data": "Click Here",
			"size": 36,
			"style": "bold",
			"name": "text1",
			"hOffset": 250,
			"vOffset": 100,
			"alignment": "center",
			"onMouseUp": "sun1.opacity = (sun1.opacity / 100) * 90;"
		},
		"div": [
			{
				"width": 20,
				"height": 30,
				"id": "dev01",
				"name": "avatar01"
			},
			{
				"width": 20,
				"height": 30,
				"id": "dev02",
				"name": "avatar02"
			},
			{
				"width": 20,
				"height": 30,
				"id": "dev03",
				"name": "avatar03"
			}
		]
	}
}

add a rest api demo for quarkus starter project

• swagger
• crud by mysql

I AS a developer want to use a clear db schema name
given jooq generating the java classes
then add "T" prefix to generated tablename

I as a reactive service wanna return reactive exception response

When an exception was throwed
Then the handler should return a uni
Scenario 1:
reactive exeption response in a reactive app
Scenario 2:
imperative exceptin response in a imperative app

introduce universal uuid generator including:

• uuid
• ksuid
• ulid
• tslid

• replace application scope by request scope

I as a designer, want to implement reactive sql crud operations
given we already implemented sql lib by jooq
then I should use the reactive feature of jooq to implement them

quarkus uses Argol as datasource connection pool, while we're trying integrate jooq and hikari, so we need to load datasource config from property file
dotEnv should be supported

employee equalsverify

introduce swagger annotation to json schema

I as a developer wanna implement reactive endpoint
when applied RequestInteceptor from jakarta-utils
then quarkus will not boot with an error hints, having block io

already tried varies method, either of them works ideas

1. blaze query , failed to work for native build
2. querydsl , lombok issues, no plugin in universe,maybe try it later
3. jpa , not so flexable

will try jooq as it can also work for native build
as the no-sql or other query like elastic search, should be used in spring when needed

introduce hash tools like:

• xxhash
• crc32
• sha256
• md5

I as a designer, wanna use jakarta instead of javax when possible
given generate tool is jsonschema2pojo
then jakarta should be used instead of javax.validation

I as a system designer, wanna test the cdi features

quarkus project got a github workflow error

delete workflow history from the Actions

smallrye config

I as a developer, wanna a reactive example
when reading/writing data to music, all the code should be reactive

per #19 we should introduce a single step in githu action to generate jacoco test report

remove this part as below
outputs:
sonar_key:
description: "sonar key"
value: ${{ steps.vars.outputs.SONAR_KEY }}

Add A camel drived demo

when open the project by vscode, build out dir was set to bin

we should use one directory , that's 'build'

I as a developer, wanna make the error info and log more clear and readable
when something happened, we'll know it clearly
Scenario 1:
when an exception occured,
then a log it triggered should have the reason

Scenario 2:
when a function or method goes smoothly,
then we can find the info and what it has done

jacoco coverage excluded entity dir from unit test, and turn to real db(from docker) for db testing in Integration test, this should be calculated, and the coverage may not necessary set to 1.0(maybe 0.85?), as real db testing for exception is really annoying

• Quarkus integration test runs after unit test each time, should be run separately
• separate test needs separate profile
• spring boot apps

as codecov will not update coverage when submiting updates of a PR #34

mv schema from shared to core

I AS a develop, need a sketelon cucumber demo
when an api is finished
then need to test the endpoint

a wasting of time and effort as we already has jacoco

as a multi module project, sonar only return 1 module

I as a system designer,wanna cache a lot of data to accelarating response speed.
given a query or objects need further process during the runtime of a process,
a bunch of data was generated, it may bring trouble when processing need more
resources and/or time, we need to cache the data to fasted the speed
Scenario 1:
when data is stored in remote systems like database or cloud services
then data should be pulled to local to accelarte the speed

Scenario 2:
when data is too big or too complex and will need lots of time for pre/pos process,
then data or middle data of some process should have these data cached to reduce the process time

Scenario 3:
when aggerageting some data
then we should cache them to make the process more easy

as this is a multi-module project, we should have templates for varies tasks, also each module can use these templates too.
templates should include these(not limited):

• build module
• test/integration test
• sonar check

for now, only versions.toml is used, better to split it into 3 files:
libs.version.toml -> libs
testlibs.version.toml ->test libs
gradlelibs.version.toml -> gradle related