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

Define global constant replacements should ignored filename #6295

Closed
4 tasks done
btea opened this issue Dec 29, 2021 · 1 comment · Fixed by #6340 or #11151
Closed
4 tasks done

Define global constant replacements should ignored filename #6295

btea opened this issue Dec 29, 2021 · 1 comment · Fixed by #6340 or #11151
Labels
enhancement New feature or request p2-nice-to-have Not breaking anything but nice to have (priority)

Comments

@btea
Copy link
Collaborator

btea commented Dec 29, 2021

Clear and concise description of the problem

When the project is built, the defined variables will be replaced. But I think the import/export variables and file names should be ignored.

Suggested solution

When the code is replaced, special variables and paths should be excluded.

Alternative

No response

Additional context

No response

Validations

@bluwy bluwy added the p2-nice-to-have Not breaking anything but nice to have (priority) label Dec 30, 2021
@patak-dev
Copy link
Member

See #7174

@patak-dev patak-dev reopened this Mar 4, 2022
@patak-dev patak-dev added enhancement New feature or request and removed enhancement: pending triage labels Mar 4, 2022
@github-actions github-actions bot locked and limited conversation to collaborators Nov 10, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
enhancement New feature or request p2-nice-to-have Not breaking anything but nice to have (priority)
Projects
None yet
3 participants