Add Support for Custom Filters
#551
Deploy Preview for atlos-docs canceled.
| Name | Link |
|---|---|
| Latest commit | fc30c87c97e75e023ecc46aecc9051c527ed2b6b |
| Latest deploy log | https://app.netlify.com/sites/atlos-docs/deploys/65f056437c11800008e8334c |
Thanks for the review!
- For the different naming of
[Unset]andNone, it seems like it is set on purpose for the tag attribute at: https://github.com/atlosdotorg/atlos/blob/9f2df58f541d29494cf49d5319f9f96ad0fa6870/platform/assets/js/app.js#L267 . Should I change"None"to"Unset"here? - Applied the other suggestions in the main comment
Ah, I see, the [Unset]/none was not something you introduced. Can we update the way we initialize TomSelect so that it displays the [Unset] tag as None (not set)? If not, then perhaps we remove this special case and just display the value as [Unset] in both the dropdown and in the tag list. Seeing None in the dropdown and [Unset] in the tag list was a bad product decision.
You can also ofc keep that out of scope for this PR and make no change, as long as filtering to unset values functions properly.
Thanks for the review! Addressed the issues in the latest commit.
P.S. love the updated date entry UI!
Awesome! Learned a lot working on this PR