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

Named formatters are interfering with DateTime formats (and others) #52

Closed
scottrippey opened this issue Mar 27, 2015 · 2 comments
Closed

Comments

@scottrippey
Copy link
Contributor

Currently, the Named Formatter syntax (eg. {0:formatter:format}) is interfering with valid formats, such as {Date:hh:mm:ss}.

@scottrippey
Copy link
Contributor Author

Possible solutions:

  1. Change the syntax so it doesn't use double-colon.
    Eg. {0,formatter:format} or one of the other discussed options.
  2. Make the named formatter feature smart -- if no formatter is found with that name, then assume it's not a named formatter.
    For example, look for a formatter hh with format mm:ss, and if it isn't found, use the default formatter with format hh:mm:ss.

@scottrippey
Copy link
Contributor Author

Sorry, duplicate of #50

axunonb pushed a commit to axunonb/SmartFormat that referenced this issue Aug 28, 2021
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