You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Inconsistent help information. The README.md file and the help messages produced with adr help new are inconsistent regarding the behavior of the -s flag. Currently, ADR does not change the status of the superseded ADR. This brings me to point 2.
Loss of semantic information. The approach taken means that, once an ADR has been created, all semantic information is lost. In this case it means that where the supersedes information should be placed is lost.
This loss of semantic information is what stalled the further development of ADR-J. Ideally, we need to know that some text such as
Superseded by ADR 3
means
Superseded by ADR {superseded_adr_id}
This also has to work when more than one ADR supersedes an ADR, or when the ADR is not superseded. This is generally a problem for any type of links that one wants to introduce.
Point 1 can be easily solved by making the documentation consistent.
Point 2 would require an extensive rewrite of ADR-J and, I suspect, would also be incompatible with the current release.
Iam trying with the ad-j tool to test adr related features and I see supercede functionality is partially working
This is the sequence of steps i followed
adr init -i madr_initial.md -t madr.md
-> Initial adr created under doc/adradr new Use Java
-> I see new adr createdadr new -s 2 use Golang
Am i missing something?
The text was updated successfully, but these errors were encountered: