-
Notifications
You must be signed in to change notification settings - Fork 64
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
Add Country.categories and Category.geographies properties #1093
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
✨
Acceptance 🍊 I've tested the whole list of methods in the original issue and I found a couple of missing ones. Let me know if we should add them:
|
Hi, it'd be great if get method for CatalogList should work with slug too. Dataset.get(<dataset_id>).variables.get(). If we do that we can say that at everypart we can find by slug or id. |
A category has no countries nor direct relation with them, so I understood that was a nested filter use case. You should do:
However, if we want to have the first option as well, I'll add it. (I already talked to Aroa last week about the fact that we seem to always have 2 ways of doing things, and it's not good.)
We discussed this a couple of weeks ago and decided (at least for the moment) to have all FK properties returning the id (but rename them to |
Sorry, it's just I was running the full acceptance cycle and I wasn't aware we decided that 😊
Let's do that validation work with @newLadyAga
|
Done @alasarr !! |
Working! and added to the demo! |
… feature/1038-add-missing-methods
…/CartoDB/cartoframes into feature/1038-add-missing-methods
Closes #1038
I added the missing methods and then I realized we could always use
get_all
for those properties so I did a bit of cleaning in code and tests ✨