log4brains icon indicating copy to clipboard operation
log4brains copied to clipboard

✍️ Log and publish your architecture decisions (ADR)

Results 58 log4brains issues
Sort by recently updated
recently updated
newest added

# Bug Report ## Description I tried to run the build command and it failed due to sharp not being found. ## Steps to Reproduce 1. yarn install --dev log4brains...

bug

# Bug Report ## Description Executing `log4brains preview` fails with Fatal `Cannot read property 'incrementalOptions' of undefined` message ## Steps to Reproduce The full log can be seen below, but...

bug

# Bug Report ## Description I had some issues with comments. ## Steps to Reproduce ### Observation 1) Put this comment at the end of any MD file: `` I...

bug

# Bug Report ## Description For any call to the CLI, there is a constant startup time of ~3 sec, whatever the command is. Even a very simple one like...

bug

Following the incident caused by a breaking change released in a dependency which does not follow semver: https://github.com/thomvaill/log4brains/issues/74 And because of these reasons: https://gajus.medium.com/stop-using-package-lock-json-or-yarn-lock-909035e94328 I think we should not use...

feature

# Bug Report ## Description When viewing ADRs in the log4brains web presentation (preview or live on gitlab / github pages), clicking on the "View in gitlab button" (![grafik](https://user-images.githubusercontent.com/1634615/151275746-417f844d-e37b-4551-9b8f-33e3460904af.png)) leads...

bug

# Feature Request ## Feature Suggestion Homebrew availability to install on macOS ## Context We are a mobile devs, as we might need to have our local ADRs, a simple...

feature

to prepare for the new release strategy of the stable versions

# Bug Report ## Description As soon as one starts filling out the "Deciders" or "Tags" section, any HTML comments start are showing up as such in the knowledge base...

bug

# Bug Report ## Description When any section of the MADR contains an HTML comment in a separate paragraph, the front end just crashes with "An unexpected error has occurred"....

bug