Ecosyste.ms: Issues

An open API service for providing issue and pull request metadata for open source projects.

GitHub / tc39/proposal-function-implementation-hiding issues and pull requests

#52 - Explain how hiding will actually work

Issue - State: open - Opened by FrameMuse about 1 year ago - 5 comments

#51 - A possible syntax form

Issue - State: open - Opened by jithujoshyjy about 2 years ago - 1 comment

#50 - Opinion: this will cause lot of "mystery bugs" in Sentry-style applications

Issue - State: open - Opened by Jabher over 2 years ago - 35 comments

#49 - Function source text serialization in error messages

Issue - State: open - Opened by bathos almost 3 years ago - 5 comments

#48 - When would these directive get used?

Issue - State: closed - Opened by theScottyJam over 3 years ago - 10 comments

#47 - Semantics of top-level directive

Issue - State: open - Opened by Huxpro almost 4 years ago - 1 comment

#46 - Provide a way to determine native implementations

Issue - State: closed - Opened by ghost almost 4 years ago - 4 comments

#45 - should non-simple parameter lists be allowed to mix with these new directives?

Issue - State: open - Opened by michaelficarra over 4 years ago - 2 comments
Labels: question

#44 - ecosystem consideration: JS self-profiling API

Issue - State: open - Opened by michaelficarra over 4 years ago

#43 - Hiding implementation of classes breaks the `is‑callable` package

Issue - State: open - Opened by ExE-Boss almost 5 years ago - 5 comments

#42 - Should "show source" be part of this proposal?

Issue - State: open - Opened by tmikov almost 5 years ago - 6 comments

#41 - What's the behavior of nested function?

Issue - State: open - Opened by hax almost 5 years ago - 4 comments

#40 - Examples of stack position information restricting refactoring

Issue - State: open - Opened by misterdjules almost 5 years ago - 12 comments

#39 - Clarification on stack frames revealing confidential information

Issue - State: closed - Opened by misterdjules almost 5 years ago - 4 comments

#38 - high-fidelity polyfill use case seems to impact error stack traces

Issue - State: closed - Opened by misterdjules almost 5 years ago - 2 comments

#36 - GetDirectiveContext broken?

Issue - State: closed - Opened by waldemarhorwat almost 5 years ago - 2 comments

#35 - Requesting more details on the motiviation for two directives

Issue - State: open - Opened by codehag almost 5 years ago - 4 comments

#34 - What if it will be used by malicious code injected by browser extension or XSS?

Issue - State: closed - Opened by JustFly1984 about 5 years ago - 6 comments

#33 - The behavior of ‘sensitive‘ on `Error.p.stack`

Issue - State: closed - Opened by lidongjies about 5 years ago - 5 comments

#31 - enumerate security properties guaranteed by the "sensitive" directive

Issue - State: closed - Opened by michaelficarra about 5 years ago - 1 comment

#30 - Appendix statement untrue for some engines

Issue - State: closed - Opened by erights about 5 years ago - 5 comments

#29 - Editorial: Fixed a typographical error in README

Pull Request - State: closed - Opened by Kriyszig about 5 years ago

#28 - Implementation of unhandled rejection/uncaught exception logging in Node.js

Issue - State: closed - Opened by misterdjules about 5 years ago - 6 comments

#27 - Impact on observability tools relying on stack traces

Issue - State: open - Opened by misterdjules about 5 years ago - 7 comments

#26 - shouldn't this proposal be dependent of the error stacks proposal?

Issue - State: closed - Opened by ghermeto over 5 years ago - 4 comments

#25 - Ability to disable the directive

Issue - State: open - Opened by ghermeto over 5 years ago - 16 comments

#24 - change the "website" URL for the repo

Issue - State: closed - Opened by michaelficarra over 5 years ago - 1 comment

#23 - reconciling the disparate function implementation hiding use cases

Issue - State: closed - Opened by michaelficarra over 5 years ago - 2 comments

#22 - Spell out stack hiding in more detail / maybe align with built-ins

Issue - State: closed - Opened by domenic over 5 years ago - 4 comments

#21 - Class-body directive prologue is incompatible with class fields

Issue - State: closed - Opened by domenic over 5 years ago - 18 comments

#20 - Interaction with other proposals and use cases

Issue - State: closed - Opened by dead-claudia over 5 years ago - 4 comments

#19 - State clearly that devtools UX is out of scope

Pull Request - State: closed - Opened by domenic over 5 years ago

#19 - State clearly that devtools UX is out of scope

Pull Request - State: closed - Opened by domenic over 5 years ago

#18 - Consider a different name besides "censorship"

Issue - State: closed - Opened by domenic over 5 years ago

#17 - combine F.p.toString and E.p.stack censorship proposals

Pull Request - State: closed - Opened by michaelficarra over 5 years ago - 5 comments

#16 - Censoring code should only be possible for native code, not userland code

Issue - State: closed - Opened by getify almost 6 years ago - 32 comments

#15 - Why describe censored code as "[native code]"?

Issue - State: closed - Opened by garvank about 6 years ago - 3 comments

#14 - Update README.md

Pull Request - State: closed - Opened by techeverri about 6 years ago

#13 - Decorator-like syntax suggestion

Issue - State: closed - Opened by littledan about 6 years ago - 15 comments

#12 - Why not censor all functions, or at least cross‑module functions?

Issue - State: closed - Opened by ExE-Boss over 6 years ago - 3 comments

#11 - This pragma is *very* long...

Issue - State: closed - Opened by dead-claudia over 6 years ago - 1 comment

#10 - Explain why we think this won't become boilerplate in every source file

Issue - State: closed - Opened by domenic over 6 years ago - 4 comments

#9 - Explain more why pragma is the best fit

Issue - State: closed - Opened by domenic over 6 years ago - 1 comment

#8 - Interaction with stacks?

Issue - State: closed - Opened by ljharb over 6 years ago - 10 comments

#7 - More info regarding the difficulties involved in "cloning" functions

Issue - State: closed - Opened by spion over 6 years ago - 2 comments

#6 - Add non-normative text clarifying what this actually does

Issue - State: closed - Opened by domenic over 6 years ago - 15 comments

#5 - "Function.prototype.toString()-Censored Code" copypasta

Issue - State: closed - Opened by domenic over 6 years ago

#4 - Motivation for pragma?

Issue - State: closed - Opened by littledan over 6 years ago - 5 comments

#3 - What should the pragma be named?

Issue - State: open - Opened by domenic over 6 years ago - 35 comments

#2 - Should this also censor `.name`?

Issue - State: closed - Opened by Jamesernator almost 7 years ago - 10 comments

#1 - Symbol?

Issue - State: closed - Opened by pocesar almost 7 years ago - 1 comment