Git Product home page Git Product logo

Comments (5)

bhb avatar bhb commented on July 22, 2024 1

@carocad Thanks for reporting this!

I agree, the "Relevant specs" section is very noisy right now.

collapse irrelevant spec pieces into ... and show only the key-predicate that failed

I have some ideas about to compact this section. One idea is to omit parts of it, as you have suggested. I am also thinking about a format like the one show in this video clip (the output of syndoc). Unfortunately, that will probably need to wait.

make relevant specs section optional and configurable when setting up the printer

Good news 😄 ! This is available today:

(binding [s/*explain-out* (expound/custom-printer {:print-specs? false})]
  (s/explain my-spec my-data))

This option has not been documented properly, but I'm going to merge in some doc fixes soon to fix this.

Please give it a try and let me know what you think.

from expound.

carocad avatar carocad commented on July 22, 2024

I am also thinking about a format like the one show in this video clip (the output of syndoc). Unfortunately, that will probably need to wait.

It looks like a very interesting way of approaching the problem :)

I think however that you should avoid trying to define (yet) another grammar language for displaying specs. I dont have a good proposal about it unfortunately, but in my experience creating mappings between two worlds always ends up with leaky abstractions and complications for the users.

from expound.

bhb avatar bhb commented on July 22, 2024

I think however that you should avoid trying to define (yet) another grammar language for displaying specs. I dont have a good proposal about it unfortunately, but in my experience creating mappings between two worlds always ends up with leaky abstractions and complications for the users.

That's a very good point. I'll think more about this.

Did the (expound/custom-printer {:print-specs? false}) work for you to just hide the "Relevant Specs" section?

from expound.

carocad avatar carocad commented on July 22, 2024

yes using :print-specs false solved the issue :)

thanks for the info

from expound.

bhb avatar bhb commented on July 22, 2024

@carocad Thanks for reporting this! Since there is an option to turn of relevant specs, I'm going to close this for now and continue to think about ways to make this section less verbose.

from expound.

Related Issues (20)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.