dOrgJelli

Hey @Niraj-Kamdar, could you provide additional details as to what the implementation of this should look like? A few questions: - How does this relate to deploying workflows as stand-alone...

Awesome I like how you broke down the 3 use-cases, and I agree. We can introduce the `polywrap.test.yaml` manifest in the future, as this will come in handy when performing...

@polywrap/dev requesting feedback

Could you get tests to pass @krisbitney? We should make sure the AssemblyScript compiler doesn't complain about these keywords-as-type-properties by adding a few more tests for commonly used keywords: const,...

I'm still a bit confused by this... why don't we just solve all naming cases (class, method, argument, property) by adding something like `m_` in AssemblyScript? Ideally we should be...

One way to approach this is to modify the URI-Resolver interface to include errors in the return structure. Additionally we could define a known set of errors for common things,...

@nerfZael do you think this can be closed now that https://github.com/polywrap/toolchain/pull/1169 is merged?

@Niraj-Kamdar @cbrzn I created this document to aggregate a backlog of ENS domains that need to be migrated. Can you please add all domains that need to be migrated to...

# Niraj Idea - dev release, prod release - dev released to any test network + dev domain (/rinkeby/dev.polywrap.eth) - prod release -> take dev domain -> set production domain...

This is blocked by ENS Text Record Support: https://github.com/polywrap/monorepo/issues/1113 Reasoning: When going through the migration backlog [here](https://hackmd.io/8QU76Ti_TUqcjDsy_Jvd3A?view) I found myself needing to create many subdomains, which is expensive and requires...