Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

define manifest data type for FIP 0031 #329

Merged
merged 4 commits into from
Mar 31, 2022

Conversation

vyzo
Copy link
Contributor

@vyzo vyzo commented Mar 23, 2022

No description provided.

FIPS/fip-0031.md Outdated
Comment on lines 145 to 146
The _Manifest_ data for version 1 (the only version currently defined) is a CID linking
to an IPLD `Vector<(String, CID)>`.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should formally define the order of this vector.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Here and, most importantly, in the system actor's state.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So whats the order? By type? Lexicographic?
I dont think it really matters all that much, but i am not opposed ti specifying it either.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

So the bundler uses a BTreeMap, which orders by actor type -- this is perfectly reasonably I guess, should we make this the standard order?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Updated to define the order by enum position.

@raulk raulk merged commit 4dce39f into raulk/finalize-fip-0031 Mar 31, 2022
@raulk raulk deleted the vyzo/fip-0031-manifest branch March 31, 2022 22:10
kaitlin-beegle pushed a commit that referenced this pull request Apr 1, 2022
* fip-0031: prepare for move to Last Call.

* define manifest data type for FIP 0031 (#329)

Co-authored-by: raulk <raul@protocol.ai>

Co-authored-by: vyzo <vyzo@hackzen.org>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants