Skip to content
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

More fine grain control on what Date columns use .timestamp vs .date, etc... #124

Open
2 tasks
xeokeri opened this issue Nov 21, 2019 · 0 comments
Open
2 tasks

Comments

@xeokeri
Copy link

xeokeri commented Nov 21, 2019

Improve DateEncodingFormat Support

There is only one way per table to set all columns using Date to one format. For example:

public static var dateEncodingFormat: DateEncodingFormat = .timestamp

or

public static var dateEncodingFormat: DateEncodingFormat = .date

Steps to Reproduce

public fileprivate(set) var date: Date
public fileprivate(set) var updated: Date

public static var dateEncodingFormat: DateEncodingFormat = .timestamp

In this example, var date: should be .date, and var updated: should be .timestamp, to be more fine grained to their respective use cases in this table.

Expected vs. Actual Behaviour

  • Expect each column to be able to independently handle date format style.
  • Actually happening, each column takes the one format.
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

No branches or pull requests

1 participant