-
Notifications
You must be signed in to change notification settings - Fork 78
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
Error in latest main branch on windrose layer ajax call #220
Comments
Ok looking at it @jywarren |
Thanks!!! This is being seen downstream as well: publiclab/plots2#5971 (comment) This is a great rehearsal for publishing new versions later! It's nice to see that |
Hey, so as you said in the call today, basically there are no tests for this layer yet in LEL. I'm figuring out writing tests. I'll start with the indigenous layers and once I'm done with that perhaps other layers will be easy. |
Awesome!
…On Tue, Jul 2, 2019 at 1:37 PM Ananya Arun ***@***.***> wrote:
Hey, so as you said in the call today, basically there are no tests for
this layer yet in LEL.
But I guess this broke some test during the integration process.
I'm figuring out writing tests. I'll start with the indigenous layers and
once I'm done with that perhaps other layers will be easy.
cc @jywarren <https://github.com/jywarren>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#220?email_source=notifications&email_token=AAAF6J47JS7YUGS4BL26DTTP5OG2RA5CNFSM4H4UGP5KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZCAUSY#issuecomment-507775563>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/AAAF6JYUAC5PJL7ZEE5LBBLP5OG2RANCNFSM4H4UGP5A>
.
|
Hey! |
Hi, ok, thanks! Does this mean we no longer need to individually include it? |
OK, i think i got the windrose one resolved by changing it's path from 'dist' to 'src'. But I'm still seeing this error in the
It all begins at this line:
here: |
Hmm, i'm really struggling with this @sagarpreet-chadha @ananyaarun can you see what's going wrong? |
It looks like we're getting a var mapknitter ;
if (!isNaN(lat) && !isNaN(lng) ){
if (image_url !== undefined){
mapknitter = L.marker([lat , lng] , {icon: redDotIcon}).bindPopup(
"<div class='mapknitter-info'><h4>"+ "<a href=" + map_page + ">" + title + "</a></h4>" +
"<p>by " + "<a href=" + url + ">" + author + "</a>" +
" near " + location +
"</p><a href=" + map_page + "><img src="+image_url+" style='width: 245px;'></a></div>"
) ;
}
} |
I see. I introduced code to check if there's an image. But now if there is no image, it passes back a null layer. Let's be sure it checks ahead of time and stops trying to make a layer. This was my fault, sorry! |
Testing |
Gah! @sagarpreet-chadha @ananyaarun my apologies, i forgot the dist files need to be built before publishing on NPM now. Doing that as |
Wait, something more complex is going on. Moving to #218 |
Resolved! |
Great !! |
Hi, all -- i'm trying to release some additional tweaks to the MapKnitter layer in #219 -- but seeing this error:
Note that in the MK code (in publiclab/mapknitter#775) we are only showing the MK layer, so I wonder if we're making an assumption that the windrose layer will be there?
@ananyaarun @sagarpreet-chadha I'm hoping this will get featured in tomorrow's release of MapKnitter 3.0, so if you have a moment to take a look that would be great! Thank you!
The text was updated successfully, but these errors were encountered: