Render nested DAO proposal details - #1559
Merged
Merged
Conversation
dnlbui
marked this pull request as ready for review
August 10, 2026 22:07
dnlbui
marked this pull request as draft
August 10, 2026 22:10
dnlbui
marked this pull request as ready for review
August 10, 2026 22:10
5 tasks
osyed
force-pushed
the
phase-5-dao-render-proposal-details
branch
from
August 11, 2026 15:03
f6a71fb to
c4fa19b
Compare
osyed
force-pushed
the
phase-5-dao-render-proposal-details
branch
from
August 11, 2026 15:09
c4fa19b to
20ecbf4
Compare
osyed
force-pushed
the
phase-5-dao-render-proposal-details
branch
from
August 12, 2026 14:28
20ecbf4 to
20616c9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
dao.repo.jstodao.js, including application and documentation references.Why
Nested DAO proposals associate each action option with a positional change set, so proposal details need to show those values together. The module rename gives the DAO data boundary a simpler filename.
Validation
node --check app.jsnode --experimental-default-type=module --test tests/dao-proposal-create.test.mjs tests/dao-summary-fetcher.test.mjs tests/dao-timeline.test.mjs