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
Weird behaviour when running pulldown marionette
#76
Comments
Yep, I added it as a set. |
Ah nice, fair enough. I wonder if to make this clearer, there should be an additional line of terminal output:
Perhaps? |
Hmm. That's a tricky one, because it all resolves itself inside pulldown-resolve (I think). Worth thinking about tho. |
Ah of course, yes. Hmm. |
@PhUU it would be good to revisit this and have a think about if it's possible... |
The obvious way would be to hit the api endpoint for a particular set to see what you get back, but in the case of [ "backbone", "backbone.marionette" ] Which ain't much use. But it's more useful than nothing, eh? The next step would be to partially resolve the identifier, util just before it becomes a URL. But it's kinda the point of pulldown that it just deals in URLs – the resolving, API and set stuff is convenience. |
But the fact that the length > 1 tells you it's a set, right? So that would be enough to at least output "OMG SETTT"? |
Oh I just re-read what you said. Yes, we can defo do that. Just make the CLI hit the API. ALL THE ACRONYMS. |
Cool, I'll work on this sometime soon :) |
Result of chat elsewhere is to make pulldown-resolve and pulldown EventEmitters, then emit |
+1. Let's get that nailed and then we can revisit this. |
it grabs backbone set too?!
The text was updated successfully, but these errors were encountered: