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.

Sign up for GitHub

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

Jump to bottom

Check the build config for errors #3

Open
lispyclouds opened this issue May 31, 2019 · 9 comments
Open

Check the build config for errors #3

lispyclouds opened this issue May 31, 2019 · 9 comments

Comments

@lispyclouds
Copy link
Member

lispyclouds commented May 31, 2019 •
edited by TimoKramer
Loading

No description provided.

@TimoKramer
Copy link
Member

there seems to be an error with schema when creating pipeline with docs/build_planned.toml

@TimoKramer
Copy link
Member

error.log

@TimoKramer
Copy link
Member

TimoKramer commented Jan 16, 2020 •
edited
Loading

maybe use the build.toml for a unit test?

TimoKramer added a commit that referenced this issue Jan 20, 2020
@TimoKramer
#3 build_planned.toml dash to underscore
887cd26
@TimoKramer
Copy link
Member

should this be an integration test? maybe all the files in docs should be tested during integration?

@lispyclouds
Copy link
Member Author

the build_planned is just a brain dump for future possibilites and should not be considered as useful. maybe mark it as such?

@TimoKramer
Copy link
Member

Is wendy still taking toml? or only json?

@lispyclouds
Copy link
Member Author

I think at this point going with edn should be the simplest option. We can think about it later if needed.

@lispyclouds lispyclouds changed the title Check the build.toml for errors Check the build config for errors Mar 4, 2023
@TimoKramer
Copy link
Member

was just asking because the toml-files are still there

@lispyclouds
Copy link
Member Author

would be good to replace them with edn. fits in well with the bb based cli approach too.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@TimoKramer @lispyclouds