Feature/92 sfmaps

[STorm175]

COOL NEW PAGE !!!!

Page name: Sfmaps

Contributors

Describe your changes

Have we discussed about this before ? (Please link the discussion link below)

Added page requirements as following:

• [ ] Page.xaml
  • [x] Change the x:Class to project namespace standard (ex: x:Class="MAUIsland.LabelPage")?
  • [x] Include xmlns:app="clr-namespace:MAUIsland"?
  • [x] Change ContentPage to app:BasePage?
  • [x] Hook the x:DataType to the ViewModel?
  • [x] Provide Padding="10" to app:BasePage?
  • [x] Provide ControlInfo to app:BasePage.Resources?
  • [x] Provide PropertiesListHeader to app:BasePage.Resources?
  • [x] Provide PropertiesListFooter to app:BasePage.Resources?
  • [x] Provide PropertyItemsSource to app:BasePage.Resources?
  • [x] Provide a brief Control Info UI ?

    <Frame Style="{x:StaticResource DocumentContentFrameStyle}">
            <Label Text="{x:StaticResource ControlInfo}" />
    </Frame>

  • [x] Provide Properties List UI ?

    <Frame Style="{x:StaticResource DocumentContentFrameStyle}">
            <CollectionView
                Footer="{x:StaticResource PropertiesListFooter}"
                Header="{x:StaticResource PropertiesListHeader}"
                ItemsSource="{x:StaticResource PropertyItemsSource}"
                Style="{x:StaticResource PropertiesListStyle}" />
    </Frame>

• [x] Page.xaml.cs
  • [x] Did you change the namespace to project namespace standard namespace MAUIsland?
  • [x] Did you remove inheritance ContentPage?
  • [ ] Did you organize everything inside region?
  • [ ] Did you change <Page>ViewModel into the constructor parmeter?
  • [ ] Did you hook the page binding context to the page view model - BindingContext = vm; ?

• [ ] PageViewModel.cs

  • [ ] Did you inherit the NavigationAwareBaseViewModel?
  • [ ] Did you organize everything inside region?
  • [ ] Did you modify the constructor like the example we provide?

    
    #region [CTor]
    public LabelPageViewModel(IAppNavigator appNavigator)
                                : base(appNavigator)
    {

  }

  endregion

Register page route requirements as following:

• [ ] Did you create now route constant ?
• [ ] Did you register page route in AppShell.xaml.cs ?
• [ ] If the page is one of applciation root route did you register it to AppShell.xaml ?

Register page services:

• [ ] Did you register the page with the view model in RegisterPages ?
• [ ] Did you register all the created services RegisterServices ?

[gitguardian[bot]]

⚠️ GitGuardian has uncovered 1 secret following the scan of your pull request.

Please consider investigating the findings and remediating the incidents. Failure to do so may lead to compromising the associated services or software components.

🔎 Detected hardcoded secret in your pull request

| GitGuardian id | Secret | Commit | Filename | | | -------------- | ------------------------- | ---------------- | --------------- | -------------------- | | [5887237](https://dashboard.gitguardian.com/incidents/5887237?occurrence=88399817) | Company Email Password | 4a4fed726e44f2f545ef267bb22c78aa7bf403f8 | src/Features/Chat/ContentViews/LoginFormContentView.xaml.cs | [View secret](https://github.com/Strypper/mauisland/commit/4a4fed726e44f2f545ef267bb22c78aa7bf403f8#diff-ad5b77d2d73242e5c454965ae6172677e9411d84e7b51fff61c4cd1f0dc9310dL33) |

🛠 Guidelines to remediate hardcoded secrets

1. Understand the implications of revoking this secret by investigating where it is used in your code. 2. Replace and store your secret safely. [Learn here](https://blog.gitguardian.com/secrets-api-management?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) the best practices. 3. Revoke and [rotate this secret](https://docs.gitguardian.com/secrets-detection/detectors/generics/company_email_password#revoke-the-secret?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). 4. If possible, [rewrite git history](https://blog.gitguardian.com/rewriting-git-history-cheatsheet?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment). Rewriting git history is not a trivial act. You might completely break other contributing developers' workflow and you risk accidentally deleting legitimate data. To avoid such incidents in the future consider - following these [best practices](https://blog.gitguardian.com/secrets-api-management/?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) for managing and storing secrets including API keys and other credentials - install [secret detection on pre-commit](https://https://docs.gitguardian.com/ggshield-docs/integrations/git-hooks/pre-commit?utm_source=product&utm_medium=GitHub_checks&utm_campaign=check_run_comment) to catch secret before it leaves your machine and ease remediation.

---

<sup>🦉 GitGuardian detects secrets in your source code to help developers and security teams secure the modern development process. You are seeing this because you or someone else with access to this repository has authorized GitGuardian to scan your pull request.

Our GitHub checks need improvements? Share your feedbacks!</sup>