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

refactor assert_is_allowed_filename and included tests #217

Conversation

naveensrinivasan
Copy link
Member

refactor assert_is_allowed_filename and included tests

Description

Fixes # (issue)

Type of change

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • This change requires a documentation update

How Has This Been Tested?

  • Test A - lind_project/tests/test_cases/test_a.c
  • Test B - lind_project/tests/test_cases/test_b.c

Checklist:

  • My code follows the style guidelines of this project
  • I have commented my code, particularly in hard-to-understand areas
  • My changes generate no new warnings
  • I have added tests that prove my fix is effective or that my feature works
  • Any dependent changes have been added to a pull request and/or merged in other modules (native-client, lind-glibc, lind-project)

refactor assert_is_allowed_filename and included tests

Signed-off-by: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>
@Yaxuan-w Yaxuan-w self-requested a review April 23, 2024 22:19
@rennergade
Copy link
Contributor

I'm going to close this PR since we have and are continuing to overhaul this file, a lot of the changes are on lines we've now deleted. Sorry for the confusion!

@rennergade rennergade closed this May 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants