Skip to content

Conversation

gkellogg
Copy link
Collaborator

@gkellogg gkellogg commented Jan 9, 2020

It might not be playing nicely with caching, please consider.

{code: 'invalid remote context', context: localCtx});
}
const importCtx = resolvedImport[0].document;
if('@import' in importCtx) {
Copy link
Member

Choose a reason for hiding this comment

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

Seems like this would need to be more involved to catch @import in scoped contexts too. There are not test for this.

Copy link
Collaborator Author

Choose a reason for hiding this comment

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

Catching it was going to require adding more state to be passed down, and even though it isn't the use case, it doesn't really cause any harm if its (mis)used this way. But, that would be an issue on the spec.

Co-Authored-By: David I. Lehn <[email protected]>
@davidlehn
Copy link
Member

Does look like maybe a caching issue could happen. I'm not sure what the situation is or if it's worth dealing with. Maybe if you use the same resources as a context and also as an import? Let's leave that alone until someone can figure out a test case.

@davidlehn davidlehn merged commit 05186bf into master Jan 27, 2020
@davidlehn davidlehn deleted the import branch January 27, 2020 22:23
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