According to Google, “Luxon is a library for dealing with dates and times in JavaScript.”
JavaScript? Couldn’t do it even if I wanted to.
DATA - Date. I guessed that I am supposed to indicate the “Expiration Date” field here.
DATA - Format. Glide has not provided any clues as to what my format options are.
I experimented by entering “yyyy” and the field properly filled with 2022.
So I tried to add “mmmm” which resulted in garbage.
I have searched in the Glide community and I have googled resulting in old Date/Time column info from two years ago. Haven’t found anything to direct me how to use this Column Type.
I know that Glide is developing and growing at an amazing rate. But to build to your “billion app developers” we still need beginner level guidance as you introduce new things.
The glide plugins documentation page has a link to the luxon documentation, which describes each of the tokens to use. They are case sensitive. I think 'LLL yyyy’or ‘MMM yyyy’ should work.
Correct. Glide has a limited set of formatting options built into a date type column. If you want to go beyond that, then you need to us the format date column. It’s a type of computed column, so it doesn’t actually hold a value, thus you still need a regular column to hold the value.
However, I do agree that it would be nice if glide provided a lot more formatting options in the standard date type column.
I also wish that they had started with the basic components of Apps when they build Pages. I understand that the user interface is designed for different layouts and that each may have unique components for their purposes, but too many of the basics aren’t comparable between the two in name or functionality.
I agree some of these advanced columns are inscrutable. We’d like to make a new ‘Add Column’ experience to replace the confusing menu, with better search, documentation, useful links, etc.:
Hidden columns will be nice if the feature makes to production: hidden in the data editor with an option to also hide them from the menus in the builder?
For a quick win, how about simply sorting the computed column list? Even after all this time, every time I create a Single Value column I find myself immediately scanning from the bottom of the list - it starts with S, so intuitively I expect it to be near the bottom
