dependencies | All 3rd party dependencies necessary for building Gaffer | Datepicker library

yarn and npm already do this job, why not use them?

Tag the dev versions when you release them

I'm thinking the suspect is an unsuccessful migration. Let's undo it and try again

Because you are executing useEffect callback whenever data changes and you are changing data in useEffect callback.

Remove data as dependency.

Use this code to fix it

Starting with 6.4 RC5 (which is the version you run as of this writing and should provide this in your original post):

The collection of thymeleaf user interface template pages are no longer found in the context root of the web application resources. Instead, they are organized and grouped into logical folders for each feature category. For example, the pages that deal with login or logout functionality can now be found inside login or logout directories. The page names themselves remain unchecked. You should always cross-check the template locations with the CAS WAR Overlay and use the tooling provided by the build to locate or fetch the templates from the CAS web application context.

https://apereo.github.io/cas/development/release_notes/RC5.html#thymeleaf-user-interface-pages

Please read the release notes and adjust your setup.

All templates are listed here: https://apereo.github.io/cas/development/ux/User-Interface-Customization-Views.html#templates

Upgrade your dagger-hilt dependencies to the same version.

Your project's root gradle file

classpath "com.google.dagger:hilt-android-gradle-plugin:2.31.2-alpha"

Your app level gradle file

implementation "com.google.dagger:hilt-android:2.31.2-alpha"

kapt "com.google.dagger:hilt-android-compiler:2.31.2-alpha"

You can do it by adding DISABLE_ESLINT_PLUGIN=true to the "build" in the "scripts" part in your package.json:

Hello I have found a solution. I had several instances running and therefore the npm start then selected a different port than I defined in the test. Have killed all processes on the port and restarted

I'm assuming you have missing dependencies on your code generation class path. Once you update your question, I'll update my answer.

jOOQ won't support your generated composite types in generated code out of the box, you'll still have to add forced type configurations for that, possibly embeddable type configurations:

• https://www.jooq.org/doc/latest/manual/code-generation/codegen-advanced/codegen-config-database/codegen-database-forced-types/
• https://www.jooq.org/doc/latest/manual/code-generation/codegen-embeddable-types/

Note that the JPADatabase offers a quick win by integrating with simple JPA defined schemas very quickly. It has its caveats. For best results, I recommend going DDL first (and generate both jOOQ code and JPA model from that), because it will be much easier to put your schema change management under version control, e.g. via Flyway or Liquibase.

As per documentation, SpringApplication converts any command line option arguments (that is, arguments starting with --, such as --server.port=9000) to a property and adds them to the Spring Environment.

-D works when running via maven. Try: java -jar application.jar --spring.config.location=file:///C://your//path//config.yml.

Via maven: mvn spring-boot:run -Dspring.config.location="file:///C://your//path//config.yml"