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

Backend doesn't allow to read Config out of the box #865

Open
mgttlinger opened this issue Aug 17, 2021 · 3 comments
Open

Backend doesn't allow to read Config out of the box #865

mgttlinger opened this issue Aug 17, 2021 · 3 comments

Comments

@mgttlinger
Copy link

I might be doing things the wrong way but it seems that the Frontend handles a ConfigsT in its transformer stack while the Backend doesn't. I can of course handle it myself but it feels like a bug or at least kind of an oddity that the Frontend allows reading from the config but the backend does not out of the box.

@alexfmpe
Copy link
Contributor

FWIW there's Obelisk.ExecutableConfig.Lookup.getConfigs :: IO (Map Text ByteString).
Not sure how that relates to Obelisk.Configs.getConfigs :: HasConfigs m => m (Map Text ByteString)), but both show up on ob hoogle when searching for getConfigs.

@mgttlinger
Copy link
Author

Yes, that is what you call the runConfigsT with, but it feels strange that I have to do this in the Backend while the Frontend does it for me.

@mgttlinger
Copy link
Author

If this is not the intended behaviour I can gladly send a PR changing that.

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

No branches or pull requests

3 participants