Skip to content

Issues: ehmpathy/declapract

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

9 Open 7 Closed
9 Open 7 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

usecase extensions should be transitive
#17 opened Dec 27, 2022 by uladkasach
summarize the results and redisplay the fails last on plan output for convinience
#14 opened Sep 17, 2021 by uladkasach
add @declapract{check.anyString} to support checking if "any string" was defined as a value of a json object key
#13 opened Sep 17, 2021 by uladkasach
add a confirmation step before applying fixes + show what the fixes will be / were
#12 opened Sep 13, 2021 by uladkasach
explicitly return failure or success flag and reason on custom check functions
#11 opened Sep 13, 2021 by uladkasach
support better default "contains" check for yml files, like we do for json files
#8 opened Sep 9, 2021 by uladkasach
1
use the .gitignore defined in the project using the declarations to add to excluded paths in glob ignore
#6 opened Sep 7, 2021 by uladkasach
when validating declarations, make sure that the example of a use case passes the use case's declarations
#3 opened Sep 5, 2021 by uladkasach
support declapract clone --declarations=... --useCase=... command
#2 opened Sep 5, 2021 by uladkasach
ProTip! What’s not been updated in a month: updated:<2024-11-30.