Skip to content

Conversation

guybedford
Copy link
Contributor

This returns an exported function for the component build to run the end-to-end component service as a fully encapsulated function call.

@guybedford guybedford force-pushed the guybedford/component-export branch from 8c29e7c to 04228f6 Compare February 2, 2023 04:59
Comment on lines +489 to +492

export fastly-runtime: interface {
serve-sync: func() -> ()
}
Copy link
Contributor

@JakeChampion JakeChampion Feb 2, 2023

Choose a reason for hiding this comment

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

non-blocking question: Would it be possible to have this in a different file which imports the xqd world?
The reason I ask is because I think it would be good to keep the xqd definition in a different file to help make it clear that the xqd definitions are not ours (also we should probably name it compute-at-edge instead of xqd 🙈 )

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Agreed, we could even explicitly name it exerpimental-compute-at-edge or something to indicate it's undergoing change.

@guybedford
Copy link
Contributor Author

Will close this out, to rather leave it to @elliottt if they want to implement something along these lines or not.

@guybedford guybedford closed this Feb 2, 2023
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