-
Notifications
You must be signed in to change notification settings - Fork 373
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
feat(examples): implement r/events
, p/authorizable
#2372
Conversation
# Conflicts: # examples/gno.land/p/demo/ownable/ownable.gno
examples/gno.land/p/demo/ownable/exts/authorizable/authorizable.gno
Outdated
Show resolved
Hide resolved
examples/gno.land/p/demo/ownable/exts/authorizable/authorizable.gno
Outdated
Show resolved
Hide resolved
examples/gno.land/p/demo/ownable/exts/authorizable/authorizable.gno
Outdated
Show resolved
Hide resolved
for Authorized; Can you check how much it related with #880? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for addressing my comments. Looks good 💪
Status update Everything is ready for merging; we have dynamically updating sections: past, upcoming and in progress events will each have their own section. I have extracted out the data from the current events page into a Go script that I will use to batch post the events instead of me manually making multiple transactions. You can see the events data up to the most recent ones here. This is how it will look like on @moul, can you please take a look at the event data and confirm everything looks good, and I will go ahead with the merge & posting of events to Portal Loop? 🙏 P.S. sorry for the weird screenshot, gnoweb does not like to cooperate |
Merging as @moul is OOO, the data in the realm is already public, and we have the ability to edit/delete anything we see fit. |
<!-- please provide a detailed description of the changes made in this pull request. --> ## Description This PR adds the r/gnoland/events realm. It handles events gno.land is attending dynamically. An admin and modetators can add new events, delete old ones, or make changes to existing ones. <details><summary>Contributors' checklist...</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [x] Added references to related issues and PRs - [x] Provided any useful hints for running manual tests - [x] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](https://github.com/gnolang/gno/blob/master/.benchmarks/README.md). </details> --------- Co-authored-by: Manfred Touron <[email protected]>
<!-- please provide a detailed description of the changes made in this pull request. --> ## Description This PR adds the r/gnoland/events realm. It handles events gno.land is attending dynamically. An admin and modetators can add new events, delete old ones, or make changes to existing ones. <details><summary>Contributors' checklist...</summary> - [x] Added new tests, or not needed, or not feasible - [x] Provided an example (e.g. screenshot) to aid review or the PR is self-explanatory - [x] Updated the official documentation or not needed - [x] No breaking changes were made, or a `BREAKING CHANGE: xxx` message was included in the description - [x] Added references to related issues and PRs - [x] Provided any useful hints for running manual tests - [x] Added new benchmarks to [generated graphs](https://gnoland.github.io/benchmarks), if any. More info [here](https://github.com/gnolang/gno/blob/master/.benchmarks/README.md). </details> --------- Co-authored-by: Manfred Touron <[email protected]>
Description
This PR adds the r/gnoland/events realm. It handles events gno.land is attending dynamically. An admin and modetators can add new events, delete old ones, or make changes to existing ones.
Contributors' checklist...
BREAKING CHANGE: xxx
message was included in the description