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

Resolved Paths are empty #62

Open
ServerlessSam opened this issue Jan 9, 2023 · 1 comment
Open

Resolved Paths are empty #62

ServerlessSam opened this issue Jan 9, 2023 · 1 comment
Milestone

Comments

@ServerlessSam
Copy link
Owner

It appears in FileLocation, the resolved paths property may be determined before substituted path is determined, which is a dependency and explains why it is an empty list. We also should solve that write_content() is building it's final location path using substituted path instead of resolved.

@ServerlessSam ServerlessSam added this to the v0.4 milestone Jan 9, 2023
@ServerlessSam
Copy link
Owner Author

Unable to replicate. It appears the logic for using subbed path instead of resolved path for write_content() is correct (see comments near method in code)

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

When branches are created from issues, their pull requests are automatically linked.

1 participant