Michael Born

Or perhaps, just "Also see 'Extensions' under 'Advanced Configuration'". Then create a new Advanced Configuration section at https://docs.bolt.cm/3.5/configuration/advanced/extensions

Looks like this section of code that renames the card: https://github.com/BaldissaraMatheus/Tasks.md/blob/main/backend/server.js#L173 could use some token replacement: ```js const newName = (ctx.request.body.name || name) .replaceAll( /\s/g, '-' ) .replaceAll(/[^a-z_-]/gi, '' )...

> I think it makes sense to keep white spaces as it makes it easier to read it in the board. Not attacking, just asking... why do filenames need to...

No worries, thanks @olivierodo !

I rebased against `development` and dropped all custom derby logic from the `build.gradle`. Seeing if tests pass.

Ok, I'm stuck now on the setUp() and teardown methods in BaseJDBCTest. Both these methods expect a derby database to be available: ``` ortus.boxlang.runtime.types.exceptions.BoxRuntimeException: Unable to create datasource connection to...

Ready for review and merge, as long as this CI run passes with bx-derby installed.

Stuck on these test failures: ``` 🧪 - src/test/java/ortus/boxlang/runtime/components/jdbc/DBInfoTest.java | ortus.boxlang.runtime.types.exceptions.DatabaseException: Unable to read foreign key info 🧪 - src/test/java/ortus/boxlang/runtime/components/jdbc/DBInfoTest.java | ortus.boxlang.runtime.types.exceptions.DatabaseException: Unable to read foreignkeys metadata 🧪 - src/test/java/ortus/boxlang/runtime/components/jdbc/DBInfoTest.java...

I'd be happy to PR a solution for either option above, just let me know!

Sounds great @olivierodo , thank you!