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

Log parameters that are : Debug with "tracing"? #84

Open
Tamschi opened this issue Jan 5, 2022 · 0 comments
Open

Log parameters that are : Debug with "tracing"? #84

Tamschi opened this issue Jan 5, 2022 · 0 comments
Labels
accepted This will be worked on domain: Rust Involves Rust code. effort: 3 Relative effort required. There's no specific unit of measurement. priority: next I'll probably get to it, eventually. state: approved Approved to proceed. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: clear A known solution is (to be) implemented.

Comments

@Tamschi
Copy link
Owner

Tamschi commented Jan 5, 2022

Is your feature request related to a problem? Please describe.

There is now tracing like this:

 INFO Request(GET /oss from 127.0.0.1:15417) Site::new  Router::new Site::render Router::render path="/oss" 0ms  WARN > HTTP 404: /oss

It would be good to automatically add fields for any parameters that are debug.
These should reflect what the parameters look like outside the component, ideally with modifiers (optional, repeat) attached.

Describe the solution you'd like

The best way to do this is likely to add field expressions. Implementing it correctly will require either autoref- or autoderef-specialisation. (The former is likely cleaner.)

Describe alternatives you've considered

This could also be enabled manually for each parameter, but I think having it available automatically is more useful overall.
Apps will need to handle passwords and such inside non-logging or opaquely-logging wrappers.

Additional context

Angular and React both have powerful in-browser development tools. It should be possible for Asteracea to hook into them automatically, somehow, since it has a somewhat similar structure.

That's a feature that could be based on this one here, though in the long run, it may be a good idea to fork one of these tools to adapt it further.

@Tamschi Tamschi added type: feature Brand new functionality, features, pages, workflows, endpoints, etc. accepted This will be worked on domain: Rust Involves Rust code. effort: 3 Relative effort required. There's no specific unit of measurement. priority: next I'll probably get to it, eventually. state: approved Approved to proceed. work: clear A known solution is (to be) implemented. labels Jan 5, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
accepted This will be worked on domain: Rust Involves Rust code. effort: 3 Relative effort required. There's no specific unit of measurement. priority: next I'll probably get to it, eventually. state: approved Approved to proceed. type: feature Brand new functionality, features, pages, workflows, endpoints, etc. work: clear A known solution is (to be) implemented.
Projects
None yet
Development

No branches or pull requests

1 participant