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

Document path to settings files #45

Open
ror3d opened this issue Nov 27, 2021 · 3 comments
Open

Document path to settings files #45

ror3d opened this issue Nov 27, 2021 · 3 comments

Comments

@ror3d
Copy link

ror3d commented Nov 27, 2021

It might be helpful to add a note to input/framework/configuration/settings.md about how the settings files are searched for starting in the working directory of the application, not in your Engine's RootPath.

My setup right now has a bit of an upside-down layout, my engine.FileSystem.RootPath is something like "../", as I have the dotnet application in a child directory.

@daveaglick
Copy link
Member

Good call! Right now I'm doing some major refactoring of the Statiq site and docs, so I'm just logging documentation improvements as issues. Once I've got that more stable, I'll start catching up on docs issues like this one. Thanks for the suggestion!

@ror3d
Copy link
Author

ror3d commented Nov 29, 2021

Awesome. Would you prefer me to submit issues like this for this kind of thing, or to bring it up in the discussion? coming at the framework without much knowledge of C# or .NET or anything, I find myself with many things I would like more easily accessible

@daveaglick
Copy link
Member

Either is fine! I'll move things around if needed. In general, I tend to think of issues as being actionable (a new feature request, a bug that needs fixing, documentation to write) and discussions as being more about examples, discussions, questions, etc. (which may result in an issue as well).

I'd say in your case (which is really valuable insight) - if it's something you've figured out and think it could use better documentation or examples for other folks, I'd say it's an issue. On the other hand, if it's something you're trying to figure out and could use some help with, open a discussion. Doesn't matter that much though, I'm around either way 😂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants