René's URL Explorer Experiment

{"@context":"https://schema.org","@type":"DiscussionForumPosting","headline":"Confusing property/get/set API","articleBody":"\u003c!--- Provide a general summary of the issue in the title above --\u003e\r\n\r\n## Expected Behavior\r\n\u003c!--- If you're describing a bug, tell us what should happen --\u003e\r\n\u003c!--- If you're suggesting a change/improvement, tell us how it should work --\u003e\r\nFor the StackFrame object, I would expect a very simple way to get and set properties:\r\n\r\n- Just access `stackframe.filename` to read the property\r\n- Set the property via `stackframe.filename = \"myfile.js\"`\r\n\r\nThat should be the API regardless of whether or not it is implemented as a getter/setter pair.  If there is extra work to do for either, then a getter/setter pair should be used with a hidden property like `stackframe._filename`, which the user should not be instructed to access directly.\r\n\r\n\r\n## Current Behavior\r\n\u003c!--- If describing a bug, tell us what happens instead of the expected behavior --\u003e\r\n\u003c!--- If suggesting a change/improvement, explain the difference from current behavior --\u003e\r\nThe current API is confusing and does not make use of actual JS getters and setters.  For example:\r\n\r\n- What happens if I set the property directly?  Is that the same as the set method?\r\n- What's different about accessing the property vs. the get method?  Both are used in the documentation with no explanation.\r\n\r\n\r\nFurthermore, the typings for the set methods have zero parameters defined.","author":{"url":"https://github.com/steverep","@type":"Person","name":"steverep"},"datePublished":"2023-08-16T19:46:55.000Z","interactionStatistic":{"@type":"InteractionCounter","interactionType":"https://schema.org/CommentAction","userInteractionCount":0},"url":"https://github.com/63/stackframe/issues/63"}