Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Separate namespaces for methods and properties? #27

Copy link
Copy link
@j-f1

Description

@j-f1
Issue body actions

Over time, it’s likely that more and more methods will be added to JSObjectRefs. Currently, there are get, set, jsValue, subscript, and (shortly) instanceof. However, at least some of these methods are likely to appear in regular JS objects (specifically get and set). While there is the escape hatch of calling object[dynamicMember: "get"] or object.get("get"), this is less than optimal and it would be great if there was a way to have a separate namespace for the JavaScriptKit-defined methods so they’d never clash with something from JS.

Maybe it would be sufficient to just add a regular subscript method object["get"] or object[1]?

Reactions are currently unavailable

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      Morty Proxy This is a proxified and sanitized view of the page, visit original site.