SSWConsulting / SSWConsulting/SSW.Rewards.Mobile

♻️Refactoring | Use XamlStyler

Open
#415 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
C#
Stars
37
Forks
11
PR merge metrics
No merged PRs in 30d

Description

Discussed in https://github.com/SSWConsulting/SSW.Rewards.Mobile/discussions/413

Originally posted by AntPolkanov February 7, 2023
Hey team,

I see a few opportunities to improve the quality of our codebase.
It would be cool if we could:

  1. Start using XamlStyler (https://github.com/Xavalon/XamlStyler). The plugin is available for both VisualStudio and Rider. It is super easy to get going; I normally use the default formatting configuration only with a few slight modifications.
    The benefit is that our xaml code will be consistently formatted across the project.
    ...

If you guys agree with it, I am happy to implement both tasks.
(cc: @matt-goldman, @JackDevAU)

It's required to:

  • Create a draft of Settings.XamlStyler
  • Discuss formatting details with @matt-goldman and make changes to the draft
  • Format all xaml files
  • Update documentation explaining how devs should set up their IDEs so that Settings.XamlStyler is picked up

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by drafting Settings.XamlStyler, then review the formatting details with @matt-goldman before applying them to all XAML files. Update the developer documentation to explain how IDEs should be configured to use the settings file; done means the checklist is complete and the project’s XAML is consistently formatted.

Written by the indexing model from the issue text.

Assessment

Tech stack
csharp
Domain
documentation, mobile, tooling
Issue type
Refactor
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.