Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Adding DatabaseService class #19

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

Conversation

ghost
Copy link

@ghost ghost commented Mar 11, 2021

Critical Changes

Changes

Issues Closed

New Metadata

Deleted Metadata

Definition of Done

Refer to Definition of Done to see any additional details for the items below:

  • Any net new LWC work has JEST test coverage 50% or above
  • Default Sa11y tests pass for all LWC components
  • 🔒 Secure both Front-end (LWC) & back-end (Apex) as necessary
  • 🔑 Grant users access in Permission Sets (Object, Field, Apex Class) as necessary
  • Link the pull request and work item by PR comment and Chatter post respectively, e.g. GUS: W-0000000: Work Name
  • Make sure that ACs are updated (if any gaps)
  • All acceptance criteria have been met
    • Developer
    • Code Reviewer
  • Pull Request contains draft release notes
  • Labels, help text, and customer facing messages are reviewed by Docs
  • QE story level testing completed

jdavilasf and others added 7 commits March 11, 2021 15:31
- Updating reference on FileController, FileService, and FileSelector to
  work with the new version of DataBaseService implemented on OFM repo.
  Also, the test classes are being updated to work with the new version
  of the UnitTest and TestUser framework.

- Updated classes:
    - FileController
    - FileController_TEST
    - FileService
    - FileService_TEST
    - FileSelector
    - FileSelector_TEST
    - DatabaseService
    - DatabaseService_TEST
    - UnitTest
    - TestUser

- Removed classes:
    - SecurityService
    - SecurityService_TEST
    - BasicStub
    - TestUtils
…to feature/231__view-requirement__complete-requirement__classes-update
Repository owner requested a review from spelak_sfemu March 12, 2021 19:38
Repository owner added the ready for dev review Ready for Developer review label Mar 12, 2021
Copy link
Mannequin

@spelak_sfemu spelak_sfemu mannequin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

See questions

@@ -71,6 +71,7 @@ public with sharing class FileService {
) {
List<Database.DeleteResult> results = new List<Database.DeleteResult>();
List<Id> contentDocumentLinkIdsToDelete = new List<Id>();
List<ContentDocumentLink> contentDocumentLinkToDelete = new List<ContentDocumentLink>();
Copy link
Mannequin

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Tweak to variable name to indicate it's a collection: contentDocumentLinksToDelete instead of contentDocumentLinkToDelete.

'System Administrator',
ADMIN_USER_EMAIL
);
User adminWithRole = createUser('System Administrator', ADMIN_USER_EMAIL);
Copy link
Mannequin

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Can we TestUser instead to create test users?

Copy over these methods and classes from the TestUser in GMS and make sure to convert "Grantseeker" to "Fundseeker" and use the profile this repo ships.

  • public static final Boolean IS_PERSON_ACCOUNTS_ENABLED = Schema.SObjectType.Account.fields.getMap().get('IsPersonAccount') != null;
  • static Id getFirstBusinessAccountRecordTypeId()
  • static Id getFirstPersonAccountRecordTypeId()
  • with sharing virtual class BusinessGrantseekerPersona extends TestUser.Persona
  • with sharing virtual class PersonGrantseekerPersona extends BusinessGrantseekerPersona

- In this commit we are removing the reference made on  the createUser
  method in FileSelector_TEST class. Now we are using the TestUser
  framework to create personas based on the test scenario.

  - FileController_TEST
  - FileSelector_TEST
  - FileService_TEST
  - TestUser
…asses-update' of github.com:SalesforceFoundation/OutboundFundsCommunity into feature/231__view-requirement__complete-requirement__classes-update
Repository owner requested a review from spelak_sfemu March 16, 2021 04:14
spelak_sfemu
spelak_sfemu mannequin approved these changes Mar 16, 2021
Copy link
Mannequin

@spelak_sfemu spelak_sfemu mannequin left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@jdavilasf , changes look good at a high level. Feel free to merge this in the parent branch so we can see the final result in the parent branch.

@spelak_sfemu spelak_sfemu mannequin added 🎯 this sprint This Pull Request is related to a Work Item committed in this sprint and removed ready for dev review Ready for Developer review labels Mar 16, 2021
Repository owner merged commit d08f35a into feature/231__view-requirement__complete-requirement Mar 16, 2021
Repository owner deleted the feature/231__view-requirement__complete-requirement__classes-update branch March 16, 2021 15:26
spelak_sfemu mannequin pushed a commit that referenced this pull request May 11, 2022
Fixes dependendabot issues:
- [Prototype Pollution in yargs-parser #9](https://github.com/SalesforceFoundation/OutboundFundsModuleSite/security/dependabot/9)
- [Exposure of sensitive information in follow-redirects #19](https://github.com/SalesforceFoundation/OutboundFundsModuleSite/security/dependabot/19)
- [Exposure of Sensitive Information to an Unauthorized Actor in follow-redirects #21](https://github.com/SalesforceFoundation/OutboundFundsModuleSite/security/dependabot/21)
- [Prototype Pollution in minimist #23](https://github.com/SalesforceFoundation/OutboundFundsModuleSite/security/dependabot/23)
spelak_sfemu mannequin pushed a commit that referenced this pull request May 12, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🎯 this sprint This Pull Request is related to a Work Item committed in this sprint
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants