microsoft / microsoft/Analysis-Services
BPA rules reaquires mm/dd/yyyy date format -- should also accept dd/mm/yyyy or yyyy-mm-dd
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 732
- Forks
- 433
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
Trying to build a BPA-Compliant model, but I just found out that date format string should follow american system, which is very confusing in europe.
Could the rule be tweaked so that other rather standard date formats such as dd/mm/yyyy or yyyy-mm-dd are accepted?
I don't want to turn off the rule, I just want it to work in a way that makes sense to me (and most people in Europe / many other places)
this is the rule: https://github.com/microsoft/Analysis-Services/blob/2bc4805910830391a470954dab1f6f63d2e7997b/BestPracticeRules/BPARules.json#L504
Thank you and regards!
@m-kovalsky is problably the one who may know if it's possible
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at BestPracticeRules/BPARules.json around line 504 and inspect how the BPA rule checks date format strings. Determine whether the rule can recognize dd/mm/yyyy and yyyy-mm-dd as well as mm/dd/yyyy; done means those formats are accepted without disabling the rule.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100