ephetic/checked-constants

Grepable typo-resistant namespaced constants

checked-constants's Issues

Research enumify etc for native solution

Frozen objects and getters that throw could do a lot of the same. Could be grepable with a definition syntax that enforced symmetry between definition and reference:

const cc = require('@ephetic/checked-constants')
cc.foo.bar.somekey = 111

where cleverness in cc allows the chain of previously undefined namespaces to be created. Would need a way to prevent grabbing object references at partial/parent paths of valid namespaces that are not themselves valid namespaces (e.g. cc.foo in previous). Would need way to keep cc extensible without namespaces being mutable, akin to #5.

Create related VSC extension

Ponder constant definitions

If a namespace can be added to anywhere, some of the desired explicitness is lost. Perhaps there should be a restriction that each namespace can only be written to once, thus requiring all constants in that namespace to be in a single multiple definition.

Alternately, if the definition syntax is sufficiently grepable that dispersed definitions are as easily found as their references, then it isn't a problem.

Implement using

e.g.

    const ns = cc.using('my/namespace')
    ns`frobulate`

Ponder how users publish registered constants

Given a module that uses this library, how would it announce to its users what constants are available? Traditionally this would be via documentation, but enums and constants objects would have tool support making this easier.

Implement isolated

e.g.

    const cc = require('checked-constants')
    const ns = cc.isolated()
    cc`foo/bar${'global'}`
    ns`foo/bar${'distinct'}`
    cc`foo/bar' //=> 'global'
    ns`foo/bar' //=> 'distinct'

Add yarn instructions

Will require packages.json changes and would be a good time for src/test refactoring.