Skip to content

Conversation

@krishna0125
Copy link

@krishna0125 krishna0125 commented Feb 20, 2025

In the docstring, the gradient dictionary keys are mentioned as float, but I believe the backend code expects them to be strings. So, I changed the docstring to reflect this, from float values (e.g., .8) to string values (e.g., ".8").

In the docstring, the gradient dictionary keys are mentioned as integers, but I believe the backend code expects them to be strings. So, I changed the docstring to reflect this, from integer values (e.g., .8) to string values (e.g., ".8").
@hansthen
Copy link
Collaborator

There is an error in the automated tests. At first glance it does not appear to be related to your change. Will have a look at it over the weekend.

@krishna0125
Copy link
Author

@hansthen , were you able to look into the error during the weekend. Please let me know if you need help on this.

@hansthen
Copy link
Collaborator

hansthen commented Mar 3, 2025

I had a look at your PR, but there seems to be an underlying issue. We did a refactor that broke passing dicts with non-string keys to Leaflet.

@hansthen
Copy link
Collaborator

hansthen commented Mar 3, 2025

Your change seems to implement a workaround for the underlying issue. Since the underlying issue is easy to fix, it seems better to me to go ahead with the fix here: #2100.

Thank you for providing a PR. Even though we will go another direction, without your PR we would not have found the underlying issue. You contribution is appreciated!

@hansthen hansthen closed this Mar 3, 2025
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