Skip to content

feat(gnovm): add importer package #2201

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

Closed
wants to merge 4 commits into from
Closed

Conversation

thehowl
Copy link
Member

@thehowl thehowl commented May 26, 2024

Supersedes #1299

WIP

@thehowl thehowl self-assigned this May 26, 2024
@github-actions github-actions bot added the 📦 🤖 gnovm Issues or PRs gnovm related label May 26, 2024
Copy link

codecov bot commented May 26, 2024

@thehowl
Copy link
Member Author

thehowl commented Oct 4, 2024

@n0izn0iz given your work on the "alternative" gnopls what do you think about using that expertise and the work creating that package driver to continue the work of this PR?

The intention is to create a system to unify:

  • How import paths and directory paths are specified, and to exactly what packages and gno files they refer to.
  • Where gno files are expected to be (gnoroot/examples? local directory? GNOHOME/packages?)

This was the intention of the work I started here, but it's complex for me to work on it at the time being, so if you had capacity to take it up I would be very glad :)

@thehowl
Copy link
Member Author

thehowl commented Dec 8, 2024

Superseded-by #2932

@thehowl thehowl closed this Dec 8, 2024
@thehowl thehowl deleted the dev/morgan/gno-resolver branch December 8, 2024 09:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
📦 🤖 gnovm Issues or PRs gnovm related 🧾 package/realm Tag used for new Realms or Packages.
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

1 participant