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

Enhance link checker and update bank data #525

Merged
merged 7 commits into from
Sep 14, 2024

Conversation

guibranco
Copy link
Owner

@guibranco guibranco commented Sep 14, 2024

Description

  • Enhanced link checker by updating the ignore list with new domains.
  • Updated bancos.json to set URLs to null for certain banks.
  • Revised documentation in bancos.md to reflect changes in bank URLs.
  • Modified SQL insert statements in bancos.sql to ensure consistency with the updated data.

Changes walkthrough 📝

Relevant files
Configuration changes
.lycheeignore
Update link checker ignore list                                                   

.lycheeignore

  • Added new domains to the ignore list.
+3/-0     
Enhancement
bancos.json
Update URLs in bancos.json                                                             

data/bancos.json

  • Set URLs to null for specific banks.
+2/-2     
bancos.sql
Update SQL for bank records                                                           

data/bancos.sql

  • Updated SQL insert statements to set URLs to null for specific banks.
  • +1/-1     
    Documentation
    bancos.md
    Update bank documentation                                                               

    data/bancos.md

    • Removed URLs for specific banks in the markdown documentation.
    +2/-2     

    Summary by CodeRabbit

    • New Features

      • Expanded the .lycheeignore file to include three new domains, improving the tool's efficiency by ignoring specified domains.
    • Bug Fixes

      • Removed URLs for "VRI Investimentos" and "Banco Pecunia" in the bank data, which may enhance data accuracy.
    • Documentation

      • Updated data/bancos.md to reflect the removal of URLs for Banco VR S.A. and Omni Banco S.A., improving clarity in the documentation.

    @guibranco guibranco linked an issue Sep 14, 2024 that may be closed by this pull request
    @gstraccini gstraccini bot added ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) good first issue A issue for someone self assign and help me =D hacktoberfest Participation in the Hacktoberfest event labels Sep 14, 2024
    Copy link

    coderabbitai bot commented Sep 14, 2024

    Walkthrough

    The pull request introduces modifications across several files, primarily focusing on the .lycheeignore file, where three new domains are added for exclusion by the Lychee tool. Additionally, the data/bancos.json, data/bancos.md, and data/bancos.sql files have been updated to remove URLs for specific bank entries, setting their Url fields to null or empty. These changes collectively impact how the tool processes web resources and the completeness of bank information.

    Changes

    File(s) Change Summary
    .lycheeignore Added domains: bancosemear.com.br, bancocedula.com.br, travelexbank.com.br.
    data/bancos.json Modified Url for "VRI Investimentos" and "Banco Pecunia" from valid URLs to null.
    data/bancos.md Cleared URL fields for Banco VR S.A. and Omni Banco S.A., changing them from specific URLs to empty.
    data/bancos.sql Updated SQL insert statements to reflect NULL values for the Url field for certain bank entries.

    Possibly related issues

    • None identified as related to the objectives of this PR.

    Possibly related PRs

    🐰 In the meadow, hopping with glee,
    New domains are hidden, just wait and see!
    URLs vanish, like dew in the sun,
    A cleaner path for the tool, oh what fun!
    With each little change, we dance and we play,
    Celebrating updates in a joyful way! 🌼✨

    Tip

    OpenAI O1 model for chat
    • We have deployed OpenAI's latest O1 model for chat.
    • OpenAI claims that this model has superior reasoning capabilities than their GPT-4o model.
    • Please share any feedback with us in the discussions post.

    Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

    Share
    Tips

    Chat

    There are 3 ways to chat with CodeRabbit:

    • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
      • I pushed a fix in commit <commit_id>.
      • Generate unit testing code for this file.
      • Open a follow-up GitHub issue for this discussion.
    • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
      • @coderabbitai generate unit testing code for this file.
      • @coderabbitai modularize this function.
    • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
      • @coderabbitai generate interesting stats about this repository and render them as a table.
      • @coderabbitai show all the console.log statements in this repository.
      • @coderabbitai read src/utils.ts and generate unit testing code.
      • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
      • @coderabbitai help me debug CodeRabbit configuration file.

    Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

    CodeRabbit Commands (Invoked using PR comments)

    • @coderabbitai pause to pause the reviews on a PR.
    • @coderabbitai resume to resume the paused reviews.
    • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
    • @coderabbitai full review to do a full review from scratch and review all the files again.
    • @coderabbitai summary to regenerate the summary of the PR.
    • @coderabbitai resolve resolve all the CodeRabbit review comments.
    • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
    • @coderabbitai help to get help.

    Other keywords and placeholders

    • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
    • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
    • Add @coderabbitai anywhere in the PR title to generate the title automatically.

    CodeRabbit Configuration File (.coderabbit.yaml)

    • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
    • Please see the configuration documentation for more information.
    • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

    Documentation and Community

    • Visit our Documentation for detailed information on how to use CodeRabbit.
    • Join our Discord Community to get help, request features, and share feedback.
    • Follow us on X/Twitter for updates and announcements.

    @gstraccini gstraccini bot added help wanted Feel free to take this issue for you and help me! 🐛 bug Issues related to bugs or errors 🔗 link checker Link checker report 🚦 awaiting triage Items that are awaiting triage or categorization labels Sep 14, 2024
    @github-actions github-actions bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Sep 14, 2024
    @penify-dev penify-dev bot added the enhancement A enhancement to the project label Sep 14, 2024
    @penify-dev penify-dev bot changed the title Link checker report Enhance link checker and update bank data Sep 14, 2024
    Copy link
    Contributor

    penify-dev bot commented Sep 14, 2024

    PR Review 🔍

    ⏱️ Estimated effort to review [1-5]

    2, because the changes are straightforward and primarily involve updating URLs and adding domains to an ignore list, which should be easy to verify.

    🧪 Relevant tests

    No

    ⚡ Possible issues

    No

    🔒 Security concerns

    No

    Copy link
    Contributor

    penify-dev bot commented Sep 14, 2024

    PR Code Suggestions ✨

    CategorySuggestion                                                                                                                                    Score
    Data integrity
    Add a valid URL for the new bank entry to maintain data integrity

    Ensure that the Url field for the new entry is not NULL or empty, as it may lead to
    inconsistencies in the database.

    data/bancos.sql [385]

    -VALUES('613','60850229','60.850.229/0001-47','Omni Banco S.A.','OMNI BANCO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,0,NULL,'Outros Créditos,Pessoal,Veículos',NULL,'2002-04-22','2021-05-27 08:00:00','2021-05-05T09:11:12.7115268-03:00','2024-05-15T16:49:45.7485284+00:00');
    +VALUES('613','60850229','60.850.229/0001-47','Omni Banco S.A.','OMNI BANCO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,0,NULL,'Outros Créditos,Pessoal,Veículos','https://www.omnibanco.com.br','2002-04-22','2021-05-27 08:00:00','2021-05-05T09:11:12.7115268-03:00','2024-05-15T16:49:45.7485284+00:00');
     
    Suggestion importance[1-10]: 8

    Why: The suggestion addresses a potential data integrity issue by ensuring that the Url field is populated, which is crucial for maintaining consistent records in the database.

    8
    Documentation integrity
    Add a valid URL for the new bank entry to maintain documentation integrity

    Ensure that the Url field for the new entry is not NULL or empty, as it may lead to
    inconsistencies in the documentation.

    data/bancos.md [389]

    -| 60850229 | 60.850.229/0001-47 | Omni Banco S.A. | OMNI BANCO S.A. | RSFN | Banco Múltiplo | DRCT | Sim | Sim | Não | Não | Sim | Não | - | Outros Créditos,Pessoal,Veículos | | 2002-04-22 | 2021-05-27 08:00:00 | 2021-05-05T09:11:12.7115268-03:00 | 2024-05-15T16:49:45.7485284+00:00
    +| 60850229 | 60.850.229/0001-47 | Omni Banco S.A. | OMNI BANCO S.A. | RSFN | Banco Múltiplo | DRCT | Sim | Sim | Não | Não | Sim | Não | - | Outros Créditos,Pessoal,Veículos | https://www.omnibanco.com.br | 2002-04-22 | 2021-05-27 08:00:00 | 2021-05-05T09:11:12.7115268-03:00 | 2024-05-15T16:49:45.7485284+00:00
     
    Suggestion importance[1-10]: 8

    Why: This suggestion is important for documentation integrity, as it ensures that the Url field is filled out, which is necessary for accurate representation of the bank entry in the documentation.

    8
    Validation
    Validate the format of the Document field to ensure compliance with CNPJ/CPF standards

    Consider validating the Document field format to ensure it adheres to expected patterns
    for Brazilian CNPJ/CPF numbers.

    data/bancos.sql [385]

    +-- Ensure the Document field follows the CNPJ/CPF format
     VALUES('613','60850229','60.850.229/0001-47','Omni Banco S.A.','OMNI BANCO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,0,NULL,'Outros Créditos,Pessoal,Veículos',NULL,'2002-04-22','2021-05-27 08:00:00','2021-05-05T09:11:12.7115268-03:00','2024-05-15T16:49:45.7485284+00:00');
     
    Suggestion importance[1-10]: 7

    Why: While validating the Document field format is a good practice for data integrity, the suggestion does not provide a concrete implementation or necessary changes to the code, making it less impactful than the previous suggestions.

    7
    Maintainability
    Review the necessity of newly added domains in the ignore list

    Ensure that the newly added domains are necessary and do not conflict with existing ignore
    patterns.

    .lycheeignore [20-22]

    +bancosemear\.com\.br
     
    -
    Suggestion importance[1-10]: 6

    Why: This suggestion is relevant and promotes maintainability, but it does not address a critical issue, as the necessity of the domains is subjective and context-dependent.

    6
    Data consistency
    Replace null with a placeholder URL for better data consistency

    Consider providing a default URL or a placeholder instead of null to ensure consistency in
    the data structure.

    data/bancos.json [9285]

    -"Url": null,
    +"Url": "https://placeholder.url",
     
    Suggestion importance[1-10]: 5

    Why: While providing a default URL could improve data consistency, the suggestion does not address a critical issue, as null values may be acceptable in this context.

    5
    Possible issue
    Verify the impact of removing existing URLs on application functionality

    Ensure that the URLs being removed are not critical to the application's functionality or
    data integrity.

    data/bancos.json [9285]

    +"Url": null,
     
    -
    Suggestion importance[1-10]: 4

    Why: This suggestion raises a valid concern, but it lacks specificity regarding the impact of the removed URLs, making it less actionable.

    4
    Best practice
    Implement URL validation to prevent setting invalid URLs

    It may be beneficial to validate the URLs before setting them to null to avoid potential
    issues with broken links.

    data/bancos.json [9285]

    -"Url": null,
    +"Url": validateUrl(url) ? url : null,
     
    Suggestion importance[1-10]: 3

    Why: The suggestion to validate URLs is a good practice, but it is not directly applicable to the current changes, as the URLs are being removed rather than validated.

    3

    Copy link

    @@ -379,10 +379,10 @@
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('599','36321990','36.321.990/0001-07','AGORACRED S/A SOCIEDADE DE CRÉDITO, FINANCIAMENTO E INVESTIMENTO','AGORACRED S/A SCFI',NULL,NULL,'RSFN',NULL,NULL,0,0,NULL,NULL,NULL,NULL,NULL,'2024-08-07',NULL,'2024-08-05T12:07:23.9850149+00:00','2024-08-05T12:07:23.9850339+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('600','59118133','59.118.133/0001-00','Banco Luso Brasileiro S.A.','BCO LUSO BRASILEIRO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,'Consignado,Imobiliário,Pessoal,Veículos','https://bancoluso.com.br/','2002-04-22','2021-12-17 10:00:00','2021-05-05T09:11:12.7115232-03:00','2024-05-15T16:49:45.7318363+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('604','31895683','31.895.683/0001-16','Banco Industrial do Brasil S.A.','BCO INDUSTRIAL DO BRASIL S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,'Consignado,Pessoal','https://www.bancoindustrial.com.br','2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115033-03:00','2024-05-15T16:49:45.7304132+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('610','78626983','78.626.983/0001-63','Banco VR S.A.','BCO VR S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,NULL,'https://www.vrinvestimentos.com.br','2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115452-03:00','2024-05-15T16:49:45.7376237+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('610','78626983','78.626.983/0001-63','Banco VR S.A.','BCO VR S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,NULL,NULL,'2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115452-03:00','2024-05-15T16:49:45.7376237+00:00');

    Check warning

    Code scanning / Tsqllint (reported by Codacy)

    Object name not schema qualified Warning

    Object name not schema qualified
    @@ -379,10 +379,10 @@
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('599','36321990','36.321.990/0001-07','AGORACRED S/A SOCIEDADE DE CRÉDITO, FINANCIAMENTO E INVESTIMENTO','AGORACRED S/A SCFI',NULL,NULL,'RSFN',NULL,NULL,0,0,NULL,NULL,NULL,NULL,NULL,'2024-08-07',NULL,'2024-08-05T12:07:23.9850149+00:00','2024-08-05T12:07:23.9850339+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('600','59118133','59.118.133/0001-00','Banco Luso Brasileiro S.A.','BCO LUSO BRASILEIRO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,'Consignado,Imobiliário,Pessoal,Veículos','https://bancoluso.com.br/','2002-04-22','2021-12-17 10:00:00','2021-05-05T09:11:12.7115232-03:00','2024-05-15T16:49:45.7318363+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('604','31895683','31.895.683/0001-16','Banco Industrial do Brasil S.A.','BCO INDUSTRIAL DO BRASIL S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,'Consignado,Pessoal','https://www.bancoindustrial.com.br','2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115033-03:00','2024-05-15T16:49:45.7304132+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('610','78626983','78.626.983/0001-63','Banco VR S.A.','BCO VR S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,NULL,'https://www.vrinvestimentos.com.br','2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115452-03:00','2024-05-15T16:49:45.7376237+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('610','78626983','78.626.983/0001-63','Banco VR S.A.','BCO VR S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,1,NULL,NULL,NULL,'2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115452-03:00','2024-05-15T16:49:45.7376237+00:00');

    Check warning

    Code scanning / Tsqllint (reported by Codacy)

    Use of unicode characters in a non unicode string Warning

    Use of unicode characters in a non unicode string
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('611','61820817','61.820.817/0001-09','Banco Paulista S.A.','BCO PAULISTA S.A.','Banco Múltiplo',NULL,'RSFN',1,1,0,0,1,0,NULL,'Consignado,Imobiliário,Troca de Modalidade','https://www.bancopaulista.com.br','2002-04-22',NULL,'2021-05-05T09:11:12.7115321-03:00','2024-05-15T16:49:45.7335337+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('612','31880826','31.880.826/0001-16','Banco Guanabara S.A.','BCO GUANABARA S.A.','Banco Múltiplo','DRCT','RSFN',0,1,0,0,NULL,NULL,NULL,NULL,'https://www.bancoguanabara.com.br','2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115029-03:00','2022-06-23T13:48:15.3478476+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('613','60850229','60.850.229/0001-47','Omni Banco S.A.','OMNI BANCO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,0,NULL,'Outros Créditos,Pessoal,Veículos','https://www.bancopecunia.com.br','2002-04-22','2021-05-27 08:00:00','2021-05-05T09:11:12.7115268-03:00','2024-05-15T16:49:45.7485284+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('613','60850229','60.850.229/0001-47','Omni Banco S.A.','OMNI BANCO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,0,NULL,'Outros Créditos,Pessoal,Veículos',NULL,'2002-04-22','2021-05-27 08:00:00','2021-05-05T09:11:12.7115268-03:00','2024-05-15T16:49:45.7485284+00:00');

    Check warning

    Code scanning / Tsqllint (reported by Codacy)

    Use of unicode characters in a non unicode string Warning

    Use of unicode characters in a non unicode string
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('611','61820817','61.820.817/0001-09','Banco Paulista S.A.','BCO PAULISTA S.A.','Banco Múltiplo',NULL,'RSFN',1,1,0,0,1,0,NULL,'Consignado,Imobiliário,Troca de Modalidade','https://www.bancopaulista.com.br','2002-04-22',NULL,'2021-05-05T09:11:12.7115321-03:00','2024-05-15T16:49:45.7335337+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('612','31880826','31.880.826/0001-16','Banco Guanabara S.A.','BCO GUANABARA S.A.','Banco Múltiplo','DRCT','RSFN',0,1,0,0,NULL,NULL,NULL,NULL,'https://www.bancoguanabara.com.br','2002-04-22','2020-11-03 06:30:00','2021-05-05T09:11:12.7115029-03:00','2022-06-23T13:48:15.3478476+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('613','60850229','60.850.229/0001-47','Omni Banco S.A.','OMNI BANCO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,0,NULL,'Outros Créditos,Pessoal,Veículos','https://www.bancopecunia.com.br','2002-04-22','2021-05-27 08:00:00','2021-05-05T09:11:12.7115268-03:00','2024-05-15T16:49:45.7485284+00:00');
    INSERT INTO Banks (COMPE,ISPB,Document,LongName,ShortName,Network,Type,PixType,Charge,CreditDocument,LegalCheque,DetectaFlow,PCR,PCRP,SalaryPortability,Products,Url,DateOperationStarted,DatePixStarted,DateRegistered,DateUpdated) VALUES('613','60850229','60.850.229/0001-47','Omni Banco S.A.','OMNI BANCO S.A.','Banco Múltiplo','DRCT','RSFN',1,1,0,0,1,0,NULL,'Outros Créditos,Pessoal,Veículos',NULL,'2002-04-22','2021-05-27 08:00:00','2021-05-05T09:11:12.7115268-03:00','2024-05-15T16:49:45.7485284+00:00');

    Check warning

    Code scanning / Tsqllint (reported by Codacy)

    Object name not schema qualified Warning

    Object name not schema qualified
    Copy link

    @coderabbitai coderabbitai bot left a comment

    Choose a reason for hiding this comment

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

    Actionable comments posted: 2

    Outside diff range and nitpick comments (1)
    data/bancos.sql (1)

    Line range hint 1-385: Review Summary

    The series of INSERT statements for the Banks table look syntactically correct and mostly consistent with the AI summary. However, please note:

    • The mentioned change for 'Omni Banco S.A.' is missing. Verify if this is an oversight and add the corresponding INSERT statement if required.

    Other than that, the SQL statements appear properly structured with consistent field names and expected data formats. Just ensure the missing entry is accounted for.

    Review details

    Configuration used: CodeRabbit UI
    Review profile: CHILL

    Commits

    Files that changed from the base of the PR and between aebd5e3 and 47379c4.

    Files ignored due to path filters (1)
    • data/bancos.csv is excluded by !**/*.csv
    Files selected for processing (4)
    • .lycheeignore (1 hunks)
    • data/bancos.json (2 hunks)
    • data/bancos.md (1 hunks)
    • data/bancos.sql (1 hunks)
    Files skipped from review due to trivial changes (1)
    • .lycheeignore
    Additional context used
    Markdownlint
    data/bancos.md

    387-387: null
    Bare URL used

    (MD034, no-bare-urls)


    388-388: null
    Bare URL used

    (MD034, no-bare-urls)

    Additional comments not posted (4)
    data/bancos.md (2)

    386-388: LGTM!

    The update to remove the URL for Banco VR S.A. looks good.

    Tools
    Markdownlint

    387-387: null
    Bare URL used

    (MD034, no-bare-urls)


    388-388: null
    Bare URL used

    (MD034, no-bare-urls)


    389-389: LGTM!

    The update to remove the URL for Omni Banco S.A. looks good.

    data/bancos.sql (2)

    Line range hint 1-1: LGTM!

    The INSERT statement for 'Banco do Brasil S.A.' looks good. The Url field is properly populated.


    382-382: Matches AI summary

    The INSERT statement for 'Banco VR S.A.' has the Url field set to NULL, which is consistent with the AI summary mentioning this change.

    @@ -9359,7 +9359,7 @@
    "Pessoal",
    "Veículos"
    ],
    "Url": "https://www.bancopecunia.com.br",
    "Url": null,
    Copy link

    Choose a reason for hiding this comment

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

    Tip

    Codebase Verification

    Inconsistency found: URL present in XML but removed from JSON

    The URL "https://www.bancopecunia.com.br" for Banco Pecunia was removed from the JSON file, but it still exists in the XML file (data/bancos.xml). This inconsistency needs to be addressed:

    • Verify if the URL removal should be applied to all data representations (JSON and XML).
    • Check if any part of the system relies on the XML data and might be affected by this inconsistency.
    • Ensure that all references to Banco Pecunia are updated consistently across the codebase.
    Analysis chain

    Verify the impact of removing the URL.

    The Url field for "Banco Pecunia" has been set to null, which is consistent with the change described in the AI-generated summary. This removes the web link associated with this bank.

    Verify if any part of the system was relying on or referencing this specific Url value. Ensure its removal does not cause any breakage.

    Scripts executed

    The following scripts were executed for the analysis:

    Script:

    #!/bin/bash
    # Description: Verify if the removed URL is referenced anywhere in the codebase.
    
    # Test: Search for the removed URL. Expect: No results. 
    rg --type-not json "https://www.bancopecunia.com.br" -A 5
    

    Length of output: 458

    @@ -9282,7 +9282,7 @@
    "PCRP": true,
    "SalaryPortability": null,
    "Products": null,
    "Url": "https://www.vrinvestimentos.com.br",
    "Url": null,
    Copy link

    Choose a reason for hiding this comment

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

    Tip

    Codebase Verification

    Synchronize URL data across JSON and XML formats

    The removal of the URL for "VRI Investimentos" in the JSON file (data/bancos.json) is inconsistent with the data in the XML file (data/bancos.xml). Both files are listed in the project's README as official data sources, which makes this inconsistency a significant issue.

    Action items:

    1. Decide whether the URL should be removed or kept for "VRI Investimentos".
    2. Update both data/bancos.json and data/bancos.xml to ensure consistency.
    3. Review and update the process for modifying bank information to ensure all data formats (JSON, XML, and any others) are updated simultaneously.
    4. Check other entries in both files to ensure there are no other inconsistencies.
    Analysis chain

    Verify the impact of removing the URL.

    The Url field for "VRI Investimentos" has been set to null, which is consistent with the change described in the AI-generated summary. This removes the web link associated with this bank.

    Verify if any part of the system was relying on or referencing this specific Url value. Ensure its removal does not cause any breakage.

    Scripts executed

    The following scripts were executed for the analysis:

    Script:

    #!/bin/bash
    # Description: Verify if the removed URL is referenced anywhere in the codebase.
    
    # Test: Search for the removed URL. Expect: No results.
    rg --type-not json "https://www.vrinvestimentos.com.br" -A 5
    

    Length of output: 464


    Script:

    #!/bin/bash
    # Description: Search for references to bancos.xml and check for documentation
    
    # Search for references to bancos.xml
    echo "Searching for references to bancos.xml:"
    rg "bancos\.xml" --type-not xml -A 5
    
    # Check for README files that might explain the relationship between JSON and XML
    echo -e "\nSearching for README files:"
    fd -e md -e txt -e rst -e adoc README
    

    Length of output: 700

    @guibranco guibranco merged commit 91dd8af into main Sep 14, 2024
    43 checks passed
    @guibranco guibranco deleted the feature/524-link-checker-report branch September 14, 2024 02:42
    Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
    Labels
    ☑️ auto-merge Automatic merging of pull requests (gstraccini-bot) 🚦 awaiting triage Items that are awaiting triage or categorization 🐛 bug Issues related to bugs or errors enhancement A enhancement to the project good first issue A issue for someone self assign and help me =D hacktoberfest Participation in the Hacktoberfest event help wanted Feel free to take this issue for you and help me! 🔗 link checker Link checker report Review effort [1-5]: 2 size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
    Projects
    None yet
    Development

    Successfully merging this pull request may close these issues.

    🔗✅ Link checker report
    1 participant