Has anyone ever seen any issues with the index vie...
# avo-2
a
Has anyone ever seen any issues with the index view displaying one value but the show view displaying a different one for the same field? (select field)
l
it might be
you can pass it a hash so the keys can differ from the values
have a look at the documentation
a
thanks
l
if you think something is not working, please open an issue on the repo
c
Still having the same issue by adding a text field. Seems to be caching issue of some sort?
l
Can you please open an issue on the link abive with some code samples and screenshots?
c
False alarm. Overlooked the
config.cache_resources_on_index_view = true
default. I'm not certain how the index view caching is setup, but we definitely weren't getting any updates to it unless we modified the object directly through the staging console or set the cache config to false.
l
Got it. We might disable that altogether
The caching takes into account the records created_at and id attributes among others
c
Thanks for the feedback Adrian! Avo has come a long way since we adopted it in the early revisions even. The caching definitely seems like a bit of a gotcha for project spin up. I think after today's run-around we'll probably disable it by default in our project setups. 🙂
l
yeah. we'll default to that as well in future versions. it stirred up too many support issues. it's clear that it's not intuitive to use